Apex Docs

# apex-docs — APEX Documentation Forge
**Version:** 2026.03.11-APEX
**Authority:** arifOS F1-F13
**Trigger:** "forge docs", "apex docs", "document this", "harden documentation"

---

## What This Skill Does

APEX-style documentation hardening using constitutional governance. Not generic "write good docs" — but *forged* documentation that reduces entropy, preserves reversibility, and links evidence.

---

## The 6-Phase APEX Flow

```
READ → RISK → REASON → FORGE → VERIFY → SEAL
```

### Phase 0: READ (Ground Truth)
```bash
# Always start here
read <target_file>
git log --oneline <target_file> | head -5
ls -la <directory_context>
```

**Output:** Actual state. Not assumed. Not "probably".

---

### Phase 1: RISK (CVSS for Docs)

| Tier | Indicator | Action |
|------|-----------|--------|
| **Critical** | Auth, payment, deletion logic undocumented | Immediate 888_HOLD |
| **High** | Public API mismatch with code | Same-day fix |
| **Medium** | Internal helper outdated | Backlog |
| **Low** | Typo, formatting | Batch |
| **Cosmetic** | "Sounds better" rewrites | Skip (PROPA) |

---

### Phase 2: REASON (F1-F4 Check)

**F1 Reversibility:**
- Can this be undone in 60 seconds?
- Git commit before edit

**F2 Truth (τ ≥ 0.99):**
- Every claim links to source
- Uncertainty stated explicitly (Ω₀)

**F4 Clarity (ΔS ≤ 0):**
- Does this reduce confusion?
- If file grows >20%, probably over-engineering

---

### Phase 3: FORGE (Minimal Delta)

**Rules:**
1. Edit, don't rewrite
2. One purpose per commit
3. No PROPA (polished performance)
4. Raw > Perfect

**Template for new sections:**
```markdown
## <Section Name>

> Source: `<file>:<line-range>`
> Last verified: `<YYYY-MM-DD>`
> Ω₀: <0.03-0.05> (uncertainty coefficient)

<Content>

<!-- If incomplete -->
**TODO:** <what's missing>
```

---

### Phase 4: VERIFY

| Check | Command |
|-------|---------|
| Links work | `grep -oP '\(.*?\)' <file> | xargs -I {} test -f {}` |
| No orphans | `comm -23 <(grep '^## ' old.md) <(grep '^## ' new.md)` |
| Grammar | `aspell check <file>` (optional) |
| F4 Clarity | Read aloud: does it reduce confusion? |

---

### Phase 5: SEAL

```bash
# Commit
git add <file>
git commit -m "<file>: <minimal description>

- Why: <F2 evidence>
- Risk: <CVSS tier>
- Reversible: <F1 check>"

# Log to memory
echo "- <file> hardened (<CVSS tier>)" >> memory/$(date +%Y-%m-%d).md
```

---

## Constitutional Constraints

### F1: Reversibility
- All changes versioned
- Can revert to pre-edit state
- 60-second recovery path

### F2: Truth
- Every claim → source link
- τ (truth coefficient) ≥ 0.99
- Unknown > Unsafe Certainty

### F4: Clarity
- ΔS ≤ 0 (entropy reduces)
- Tables > Lists > Prose
- No PROPA

### F7: Humility
- State Ω₀ (uncertainty)
- Mark TODOs explicitly
- "This section needs review"

### F11: Command Auth
- Destructive (delete, rewrite) → propose
- Wait for F13 "do it"

### F12: Injection Defense
- Sanitize external inputs before including
- No exec of extracted content

### F13: Sovereignty
- Human veto absolute
- "Don't like it" = valid rejection

---

## Drift Detection

**Weekly scan:**
```bash
# Check for orphaned docs
for doc in *.md; do
  refs=$(grep -oP 'source:\s*\K[^\s]+' "$doc" | sort -u)
  for ref in $refs; do
    test -f "$ref" || echo "ORPHAN: $doc references missing $ref"
  done
done
```

**Monthly audit:**
- Compare code exports to doc coverage
- Flag undocumented public functions
- Update last_verified dates

---

## Example Workflow

**User:** "Harden AGENTS.md"

**Agent:**
1. READ → `cat AGENTS.md`, check git history
2. RISK → Public API access map → Critical tier
3. REASON → F1: reversible (git) ✓, F2: needs evidence links ✓, F4: ΔS? needs audit
4. FORGE → Add source links to §4, mark Ω₀ where uncertain
5. VERIFY → Links work, no orphans, clarity check
6. SEAL → Commit, log to memory/2026-03-11.md

---

## Anti-Patterns (Never Do)

| Anti-Pattern | Why | Alternative |
|--------------|-----|-------------|
| "Documentation sprint" | Bulk rewrite = irreversible | One file at a time |
| "Polish pass" | PROPA — no substance | Skip if content correct |
| "Perfect grammar" | Cosmetic, not clarity | Raw transmission OK |
| "v2, v3, final" | File explosion | Edit in place |
| AI writes, human skips review | Hallucination risk | Human must verify F2 |

---

## Quick Reference

```bash
# Start any doc hardening
apex-docs harden <file>

# Check drift
apex-docs drift-scan <directory>

# Verify single file
apex-docs verify <file>
```

---

*Ditempa bukan diberi*