chore: fill derivable placeholders, drop false ARCHITECTURE, surface the rest

[hyperpolymath]

Automated estate top-up. Nothing here invents a value.

Filled — every token with one mechanical answer (owner, repo, forge, author, dates, project name, main branch). Identity from the git remote, dates from the clock, name from the README H1.

Not filled, on purpose — SECURITY_EMAIL (two competing addresses exist in the estate), RESPONSE_TIME, CONDUCT_TEAM (substitutes into "a {{CONDUCT_TEAM}} member", which is not English), WEBSITE, PROJECT_DESCRIPTION, LANG_STACK. More than one defensible answer exists, and a confident wrong value is worse than a visible gap.

Deleted — ARCHITECTURE.md where it is byte-identical to the 346-copy estate boilerplate (blob 607e3d8c). Those 33 lines describe a src/ tests/ docs/ scripts/ config/ tree this repo does not have. Matched by hash, so a genuinely written ARCHITECTURE can never be caught by it.

CODEOWNERS — the solo form from standards/CODEOWNERS-POLICY.adoc Rule 1, which forbids a catch-all where the only owner is the sole maintainer. templates/CODEOWNERS contradicts that policy; the policy is versioned, dated and resolves standards#55, so it wins. Genuine co-owners (Rule 2) are untouched.

Surfaced — REQUIRES_INITIALISATION.md plus a priority action in 0-AI-MANIFEST.a2ml, listing every remaining token, what it means, which files it belongs in, why it was not done already, and that it is to be deleted only when the work is genuinely complete.

Built from a fresh clone of origin/main, never a local checkout — several of those are dirty and hold unpushed commits.

🤖 Generated with Claude Code

[gitar-bot]

⚠️ Bug: Placeholder substitution corrupted STATE.a2ml guard patterns

The top-up pass substituted the project name into the guards' own reject lists, turning the {{PROJECT}} detection token into the literal JANUSKEY. This has two bad effects: (1) the guards no longer detect an unfilled {{PROJECT}} placeholder in STATE.a2ml — the very template-staleness case they exist to catch now passes silently; (2) they will now reject/warn on any legitimate STATE.a2ml that contains the string JANUSKEY (e.g. an uppercased project name in a heading or field), producing false positives. Restore the meta-token {{PROJECT}} in both reject-if-contains and reject_patterns — it is a guard vocabulary term, not a value to be filled.

Fix 1: methodology.a2ml line 104: keep the placeholder token, not the substituted name.

reject-if-contains = ["{{PLACEHOLDER}}", "{{PROJECT}}", "rsr-template-repo"]

• Apply fix

Fix 2: methodology-guard.k9.ncl line 64: keep the placeholder token, not the substituted name.

reject_patterns = ["{{PLACEHOLDER}}", "{{PROJECT}}", "rsr-template-repo"],

• Apply fix

_{Check a box to apply a fix or reply for a change | Was this helpful? React with 👍 / 👎}

[gitar-bot]

⚠️ This PR is blocked due to unresolved code review findings.

_{Configure merge blocking · Maintainers can dismiss this review.}

[gitar-bot]

Note

Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime.
Learn more

Code Review ⚠️ Changes requested 0 resolved / 1 findings

Automated estate top-up fills derivable placeholders and drops boilerplate architecture docs, but placeholder substitution corrupted STATE.a2ml guard patterns by injecting the literal project name.

⚠️ Bug: Placeholder substitution corrupted STATE.a2ml guard patterns

📄 .machine_readable/self-validating/methodology-guard.k9.ncl:64

The top-up pass substituted the project name into the guards' own reject lists, turning the {{PROJECT}} detection token into the literal JANUSKEY. This has two bad effects: (1) the guards no longer detect an unfilled {{PROJECT}} placeholder in STATE.a2ml — the very template-staleness case they exist to catch now passes silently; (2) they will now reject/warn on any legitimate STATE.a2ml that contains the string JANUSKEY (e.g. an uppercased project name in a heading or field), producing false positives. Restore the meta-token {{PROJECT}} in both reject-if-contains and reject_patterns — it is a guard vocabulary term, not a value to be filled.

methodology.a2ml line 104: keep the placeholder token, not the substituted name.

reject-if-contains = ["{{PLACEHOLDER}}", "{{PROJECT}}", "rsr-template-repo"]

methodology-guard.k9.ncl line 64: keep the placeholder token, not the substituted name.

reject_patterns = ["{{PLACEHOLDER}}", "{{PROJECT}}", "rsr-template-repo"],

🤖 Prompt for agents

Code Review: Automated estate top-up fills derivable placeholders and drops boilerplate architecture docs, but placeholder substitution corrupted STATE.a2ml guard patterns by injecting the literal project name.

1. ⚠️ Bug: Placeholder substitution corrupted STATE.a2ml guard patterns
   Files: .machine_readable/self-validating/methodology-guard.k9.ncl:64

   The top-up pass substituted the project name into the guards' own reject lists, turning the `{{PROJECT}}` detection token into the literal `JANUSKEY`. This has two bad effects: (1) the guards no longer detect an unfilled `{{PROJECT}}` placeholder in STATE.a2ml — the very template-staleness case they exist to catch now passes silently; (2) they will now reject/warn on any legitimate STATE.a2ml that contains the string `JANUSKEY` (e.g. an uppercased project name in a heading or field), producing false positives. Restore the meta-token `{{PROJECT}}` in both `reject-if-contains` and `reject_patterns` — it is a guard vocabulary term, not a value to be filled.

   Fix (methodology.a2ml line 104: keep the placeholder token, not the substituted name.):
   reject-if-contains = ["{{PLACEHOLDER}}", "{{PROJECT}}", "rsr-template-repo"]

   Fix (methodology-guard.k9.ncl line 64: keep the placeholder token, not the substituted name.):
   reject_patterns = ["{{PLACEHOLDER}}", "{{PROJECT}}", "rsr-template-repo"],

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

---

Important

Your trial ends in 5 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more.

_{Was this helpful? React with 👍 / 👎 | Gitar}