Skip to content

frontier-readiness: gap #5 audit — AUTONOMOUS-LOOP.md + WONT-DO.md (batched)#186

Merged
AceHack merged 1 commit intomainfrom
frontier-readiness/audit-autonomous-loop-and-wont-do
Apr 23, 2026
Merged

frontier-readiness: gap #5 audit — AUTONOMOUS-LOOP.md + WONT-DO.md (batched)#186
AceHack merged 1 commit intomainfrom
frontier-readiness/audit-autonomous-loop-and-wont-do

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 23, 2026

Summary

AUTONOMOUS-LOOP.md

9 sections, all Claude Code harness discipline. Cron mechanism / tick sentinel / every-tick checklist / escalation / session-restart / etc. No Zeta-library content. Refactor effort: ~0 — Frontier inherits verbatim.

WONT-DO.md

6 sections: preamble + 5 entry-categories.

  • Shape (preamble / status vocab / entry template / "How to add") → factory-generic
  • Entry content (Algorithms / Engineering / Out-of-scope for DBSP library / Personas / ...) → heavily Zeta-specific

Strategy: Frontier inherits shape + empty stubs; Zeta retains entries. Repo/process section mixed — entry-by-entry review at split time. Effort: M.

Progress tally (8 audits)

File Class Effort
CLAUDE.md both S
AGENTS.md both M
GOVERNANCE.md (#181) factory-generic S
CONFLICT-RESOLUTION.md (#183 merged) both M
AGENT-BEST-PRACTICES.md (#184) factory-generic S
ALIGNMENT.md (#185) factory-generic S
AUTONOMOUS-LOOP.md (this) factory-generic ~0
WONT-DO.md (this) both M

8 of ~16 → halfway mark. Projected completion ~Otto-23.

Attribution

Otto (loop-agent PM hat); two-file batch cadence this tick.

🤖 Generated with Claude Code

…atched)

Two-file batch this tick. Seventh and eighth audits in
gap #5.

AUTONOMOUS-LOOP.md: factory-generic (cleanest so far).
9 sections, pure Claude Code harness discipline, zero
Zeta-library content. Refactor effort: ~0 (verbatim to
Frontier).

WONT-DO.md: both (coupled). Shape (entry template, ADR
status vocabulary, "How to add" section) is factory-
generic; 5 of 6 entry-sections are Zeta-library-specific
("Algorithms / operators", "Engineering patterns",
"Out-of-scope for a DBSP library", etc.). Refactor
strategy: Frontier inherits shape + empty section stubs;
Zeta retains full current entries as library decision
record. Effort: M.

Progress: 8 of ~16 files audited (Otto-7/9/10/12/13/14/15).
At halfway mark; projected completion ~Otto-23.

Pattern tally now 8 audits:
- factory-generic: GOVERNANCE / AGENT-BEST-PRACTICES /
  ALIGNMENT / AUTONOMOUS-LOOP (4)
- both (coupled): CLAUDE / AGENTS / CONFLICT-RESOLUTION /
  WONT-DO (4)

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 23, 2026 19:44
@AceHack AceHack enabled auto-merge (squash) April 23, 2026 19:44
AceHack added a commit that referenced this pull request Apr 23, 2026
…-DO); halfway mark

Seventh + eighth audits landed in a single tick. Batched
cadence proven: 2× audit throughput at similar tick
overhead as single-file ticks.

AUTONOMOUS-LOOP.md: factory-generic (cleanest; zero
refactor). Otto's own operating spec inherits verbatim —
any Claude-Code-using adopter gets the autonomous-loop
discipline free.

WONT-DO.md: both (coupled). Shape transfers; Zeta-specific
entries stay in Zeta's library decision record.

Progress: 8 of ~16 files = halfway. Balanced tally 4
factory-generic + 4 both-coupled.

PR #186 armed. Seven PRs now simultaneously armed (#165/
#178/#181/#182/#184/#185/#186) — free-tier CI throughput
is the bottleneck.

Attribution: Otto (loop-agent PM hat).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@AceHack AceHack merged commit 03a1112 into main Apr 23, 2026
12 checks passed
@AceHack AceHack deleted the frontier-readiness/audit-autonomous-loop-and-wont-do branch April 23, 2026 19:46
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 65a61734ac

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

| "Engineering patterns" | zeta-library-specific (mostly) | Likely Zeta-specific engineering decisions (exception handling / async patterns / wire format / etc.). Needs entry-by-entry review to confirm all; may contain a few factory-shape entries. |
| "Repo / process" | **both** | Repo / process decisions range from factory-generic (CI policy / merge-gate patterns) to Zeta-specific (openspec structure decisions). Entry-by-entry mixed. |
| "Out-of-scope for a DBSP library" | zeta-library-specific | Explicitly scoped to DBSP library domain by section name. Full Zeta. |
| "Personas and emulation" | factory-generic | Persona-framework decisions (emulation scope, conflict-handling) transfer to any adopter running named personas. |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reclassify persona section as split-coupled content

Marking Personas and emulation as factory-generic is inconsistent with the source it summarizes: docs/WONT-DO.md contains a maintainer-specific active-instance entry (including a named individual and project-local memory path), so treating this section as transferable will cause split planning to move project-specific policy into Frontier instead of keeping it in Zeta or templating it. This can misdirect the gap #1 extraction workflow and propagate non-generic content to adopters.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the ongoing “factory vs Zeta” separation audit to include classifications for two additional documentation files as part of Frontier-readiness gap #5.

Changes:

  • Updates the “Files audited” / “Files to audit” lists to reflect newly audited documents.
  • Adds audit writeups for docs/AUTONOMOUS-LOOP.md (factory-generic) and docs/WONT-DO.md (both/coupled) including section-by-section breakdown and refactor notes.


**File location post-split:** Frontier as-is.

**Length:** 483 lines. **9 sections.**
Copy link

Copilot AI Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The recorded line count for docs/AUTONOMOUS-LOOP.md looks stale. In the current tree it is 484 lines (not 483), so this audit entry will drift as the target file changes. Consider either updating the number or removing hard-coded line counts to avoid ongoing maintenance churn.

Suggested change
**Length:** 483 lines. **9 sections.**
**Structure:** 9 sections.

Copilot uses AI. Check for mistakes.
status vocab + entry schema) → Frontier. Zeta-specific
entries → Zeta repo's own WONT-DO.md at split time.

**Length:** 626 lines. **6 top-level sections.**
Copy link

Copilot AI Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docs/WONT-DO.md metadata here appears inconsistent with the current file. The repo copy is 627 lines (not 626), and it contains 7 ## sections (including “What the statuses mean” and “How to add an entry”). Please reconcile the stated counts with the actual document structure, or avoid hard-coding these numbers.

Suggested change
**Length:** 626 lines. **6 top-level sections.**
**Shape:** Medium-sized policy log with a factory-generic
preamble/status vocabulary, several substantive declined-work
sections, and a factory-generic "How to add an entry"
appendix.

Copilot uses AI. Check for mistakes.
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.

2 participants