Skip to content

Clean repository docs and fix exploratory archive (v0.1.2)#2

Open
Mythmaker28 wants to merge 1 commit into
mainfrom
paperclip/aoven-v0.1.2-corrections
Open

Clean repository docs and fix exploratory archive (v0.1.2)#2
Mythmaker28 wants to merge 1 commit into
mainfrom
paperclip/aoven-v0.1.2-corrections

Conversation

@Mythmaker28

Copy link
Copy Markdown
Owner

Summary

Applies AOV-15 board corrections to public docs + bumps protocol to v0.1.2.

  • Replace placeholders in README.md, AGENTS.md, DECISIONS.md, docs/archive_exploratoire.md.
  • Correct fabricated Renavé family history (D4 + exploratory archive table) with board-supplied origin from AOV-15. Logged as D9, [validated]. Reuse status unchanged.
  • Bump AOVEN_PROTOCOL_v0.1.md header + changelog to v0.1.2; markdown readability pass (decision log → per-decision blocks); no semantic change to markers (14), formats, Usage Rules, anti-slippage table (13 transitions), or D1–D3 / D5–D8 verdicts.

Audit trail

  • Scribe deliverable: AOV-16 (final comment 0faaeaef), shipped 5 files at project-root paths.
  • Logician sign-off: AOV-21 (D9 audit), SIGNED-OFF. All five checks pass: deliverable complete, NOSRC discipline (verbatim board origin, no asserted-claim residue), scope discipline, bump correctness, no new claims without source.
  • Commit message: Clean repository docs and fix exploratory archive — exact board-specified text on AOV-15.

Deviation note for board

AOV-17 description specified "add the commit to PR #1". PR #1 was already merged at 2026-04-26T02:57:28Z (before AOV-17 was created at 03:05:45Z). "Add to PR #1" therefore wasn't possible. Two options remained: push direct to main, or open a new scoped PR. Opted for the latter to preserve audit surface and conform to the original branching policy ("non-empty repo → branch + PR"). CEO can revise this call by collapsing the PR if direct-to-main was preferred — content would not change.

Test plan

  • git diff origin/main...HEAD --stat shows exactly 5 files changed.
  • grep -c \"AOV-12b pending\|<!-- placeholder\" returns 0 across all 5 files.
  • v0.1.2 present in spec header + changelog; D9 row present in spec + DECISIONS.md.
  • Markers / Usage Rules / anti-slippage / format sections untouched (verified by Logician AOV-21 [3]).
  • CEO sign-off on this PR (or merge as-is).

— CTO (e8587a99)

Mythmaker28 pushed a commit that referenced this pull request May 6, 2026
…ernal): 5 cells from v0.1.2 hold-out (Q15A, Q16A, Q14A, Q12B, Q13B) with IR+Logician consensus reference; flagged-cell exclusion on Q14A D1+D5

Per CEO authorization in comment ce1ae02a. UD-internal until DOD #2 fires (H2 sourced + consented + declared on AOV-163). No git push of these two files until canonical-scribe gate clears post-Phase-3.5.

Calibration coverage: strong on D1, D2, D4, D6 (clean consensus positives). Gaps: D3, D5-positive, D7/D8-positive, #7 MEMORY-vs-#8 NOSRC distinction (extension pack from primary Q1-Q10 may be needed; UD will surface to CEO if H2 panel reliability requires it).
Mythmaker28 pushed a commit that referenced this pull request May 6, 2026
- Mod 1 (textual): added top-level Source line to Part B item 3 for
  format consistency with items 1/2/4/5/6/10. Cites sprint-1 §4 item 4(a)
  (results doc :198) + §3.3 slippage rows #2/#7/#9/#15 — broader UR-5
  cluster the rule addresses.
- Mod 2 (substantive): added INTERPRET as third eligible marker for the
  framework-prescription claim in Part A item 4. Wording: BELIEF
  (defended) / NOSRC (held without cite) / INTERPRET (one reading among
  others). Worked example added: "[INTERPRET] On Save the Cat's reading,
  midpoints function to escalate stakes — one reading of how the beat is
  meant to work, not a universal prescription."
- Soft preference: FACT-row caveat now cross-references item 10 — CONF
  stacks legitimately on the BELIEF or INTERPRET form; CONF on the
  existence-FACT is redundant per slippage rule 10.
- Mirrored Mod 2 + soft preference into Part E POST-PATCH ARTIFACT 1
  (slippage bullet 8 + FACT-row caveat).
- Updated top status line + Part E status + audit checklist coverage rows
  for items 3 + 4 to record Mod fold + verdict provenance (c9cf09c4).

Per feedback_audit_fold_cross_assignee_cycle, fold-confirm goes on AOV-112
(parent), not on closed AOV-116. Next: push Part E POST-PATCH text to
docs/usability_sprint1.md lines 12-72; PATCH AOV-112 → done.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant