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: Justfile syntax mis-flagged as unfilled template tokens

REQUIRES_INITIALISATION.md and the 0-AI-MANIFEST.a2ml priority-action block instruct a reader/agent to resolve {{ARGS}}, {{REPO_PATH}} and {{VERSION}} as outstanding substitution placeholders, but these are native just interpolation of recipe parameters (run *ARGS: -> {{ARGS}}, hook-install REPO_PATH: -> {{REPO_PATH}}, release VERSION: -> {{VERSION}} in Justfile:148,160,193). They are correct, permanent justfile syntax, not template gaps. An agent following the instructions to "resolve what you legitimately can" could edit the Justfile and break the recipes, and since these tokens can never legitimately be removed, the file's own deletion rule ("delete only when no token below remains anywhere in the tree") can never be satisfied. Exclude just variable interpolation from the token scan, or remove these three entries and drop REQUIRES_INITIALISATION.md if no genuine template tokens remain.

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

[gitar-bot]

💡 Quality: Markdown/HTML block appended into TOML-like .a2ml file

The appended block uses Markdown ## headings and <!-- BEGIN/END --> HTML comments, but 0-AI-MANIFEST.a2ml is a TOML-like format using // comments and [section] headers. No tool currently parses .a2ml so there is no runtime break, but if a strict parser is ever added this trailing free text after the [invariants] table will fail. Consider expressing the notice within the file's own comment/section syntax.

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

[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 / 2 findings

Automated repository estate top-up that fills derivable placeholders and drops boilerplate documentation, but introduces a syntax error in the Justfile and malformatted headers in the AI manifest file.

⚠️ Bug: Justfile syntax mis-flagged as unfilled template tokens

📄 REQUIRES_INITIALISATION.md:42-56 📄 0-AI-MANIFEST.a2ml:80-83

REQUIRES_INITIALISATION.md and the 0-AI-MANIFEST.a2ml priority-action block instruct a reader/agent to resolve {{ARGS}}, {{REPO_PATH}} and {{VERSION}} as outstanding substitution placeholders, but these are native just interpolation of recipe parameters (run *ARGS: -> {{ARGS}}, hook-install REPO_PATH: -> {{REPO_PATH}}, release VERSION: -> {{VERSION}} in Justfile:148,160,193). They are correct, permanent justfile syntax, not template gaps. An agent following the instructions to "resolve what you legitimately can" could edit the Justfile and break the recipes, and since these tokens can never legitimately be removed, the file's own deletion rule ("delete only when no token below remains anywhere in the tree") can never be satisfied. Exclude just variable interpolation from the token scan, or remove these three entries and drop REQUIRES_INITIALISATION.md if no genuine template tokens remain.

💡 Quality: Markdown/HTML block appended into TOML-like .a2ml file

📄 0-AI-MANIFEST.a2ml:76-90

The appended block uses Markdown ## headings and <!-- BEGIN/END --> HTML comments, but 0-AI-MANIFEST.a2ml is a TOML-like format using // comments and [section] headers. No tool currently parses .a2ml so there is no runtime break, but if a strict parser is ever added this trailing free text after the [invariants] table will fail. Consider expressing the notice within the file's own comment/section syntax.

🤖 Prompt for agents

Code Review: Automated repository estate top-up that fills derivable placeholders and drops boilerplate documentation, but introduces a syntax error in the Justfile and malformatted headers in the AI manifest file.

1. ⚠️ Bug: Justfile syntax mis-flagged as unfilled template tokens
   Files: REQUIRES_INITIALISATION.md:42-56, 0-AI-MANIFEST.a2ml:80-83

   REQUIRES_INITIALISATION.md and the 0-AI-MANIFEST.a2ml priority-action block instruct a reader/agent to resolve `{{ARGS}}`, `{{REPO_PATH}}` and `{{VERSION}}` as outstanding substitution placeholders, but these are native `just` interpolation of recipe parameters (`run *ARGS:` -> `{{ARGS}}`, `hook-install REPO_PATH:` -> `{{REPO_PATH}}`, `release VERSION:` -> `{{VERSION}}` in Justfile:148,160,193). They are correct, permanent justfile syntax, not template gaps. An agent following the instructions to "resolve what you legitimately can" could edit the Justfile and break the recipes, and since these tokens can never legitimately be removed, the file's own deletion rule ("delete only when no token below remains anywhere in the tree") can never be satisfied. Exclude `just` variable interpolation from the token scan, or remove these three entries and drop REQUIRES_INITIALISATION.md if no genuine template tokens remain.

2. 💡 Quality: Markdown/HTML block appended into TOML-like .a2ml file
   Files: 0-AI-MANIFEST.a2ml:76-90

   The appended block uses Markdown `##` headings and `<!-- BEGIN/END -->` HTML comments, but 0-AI-MANIFEST.a2ml is a TOML-like format using `//` comments and `[section]` headers. No tool currently parses .a2ml so there is no runtime break, but if a strict parser is ever added this trailing free text after the `[invariants]` table will fail. Consider expressing the notice within the file's own comment/section syntax.

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}

[gitar-bot]

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

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

[hyperpolymath]

Closing in favour of a reworked substituter — hyperpolymath/standards#590.

This sweep filled {{TOKEN}} placeholders by plain text replacement across every file. Across the 90 repositories reviewed it drew 141 findings, and one is severe:

sed "s/{{PROJECT_NAME}}/$name/g"  →  sed "s/Conative Gating/$name/g"
sed -e "s/{{DATE}}/$DATE/g"       →  sed -e "s/2026-08-05/$DATE/g"

Those are the scripts whose job is to perform template substitution. Filling the left-hand side of their own sed expressions means template application silently stops working — and the breakage stays invisible until someone mints a repository from the template and gets a half-substituted tree.

Four further shapes came out of the same cause:

• release.sh no longer substitutes {{DATE}} into release notes
• just's own {{ARGS}} reported as an unfilled token, leaving repos permanently "not initialised"
• instructional docs rewritten to "Replace laminar, laminar, {{DEPS}} with actuals"
• documentation describing placeholders had its examples filled in

The rule plain replacement cannot express: a placeholder is sometimes a value to fill and sometimes the subject being discussed. standards#590 encodes that distinction and is tested against this exact corruption (9/9, the first three cases reproducing it).

Nothing here is lost — the placeholder filling will be redone with that tool. Closing rather than fixing forward because repairing 289 branches individually would repeat the mistake at the same scale.