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]

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

Fills derivable metadata placeholders and cleans up template boilerplates across the repository, but hardcodes repository slugs to 'bag-of-actions' and flags native Just syntax {{ARGS}} as an unfilled token.

⚠️ Bug: {{ARGS}} flagged as unfilled token but is native Just syntax

📄 REQUIRES_INITIALISATION.md:42-49 📄 Justfile:58-59 📄 .machine_readable/contractiles/Justfile

REQUIRES_INITIALISATION.md lists {{ARGS}} as a substitution token still needing a value, but {{ARGS}} is Just's own positional-argument interpolation for the invariant-path *ARGS: recipe (./scripts/invariant-path.sh {{ARGS}}), not an estate placeholder. This is a false positive: a reader/agent instructed to 'resolve' it would break the recipe, and because this interpolation never disappears from the tree, the file's own deletion criterion ('delete only when no token below remains anywhere in the tree') can never be met — the gate never goes green, defeating the file's purpose. Exclude Just's {{ARGS}}/{{ARG}} recipe interpolations from the token scan (they are always paired with a *ARGS/parameter declaration) and regenerate the file; here it should report zero outstanding tokens.

⚠️ Bug: Issues/registry URLs hardcoded to bag-of-actions, not remote slug

📄 Justfile:704 📄 .machine_readable/contractiles/Justfile:604

The diff replaced {{OWNER}}/{{REPO}} with the literal hyperpolymath/bag-of-actions (issues link and container-matrix registry), but the actual git remote for this repository is github.com/hyperpolymath/continuation-mesh. The PR states identity was derived from the git remote, yet the value substituted is the internal project name, not the remote slug. If hyperpolymath/bag-of-actions is not a rename-aliased repo, just help-me will send bug reporters to a 404. Verify the canonical slug and substitute continuation-mesh (or confirm the GitHub rename redirect exists) so the issue link resolves.

🤖 Prompt for agents

Code Review: Fills derivable metadata placeholders and cleans up template boilerplates across the repository, but hardcodes repository slugs to 'bag-of-actions' and flags native Just syntax {{ARGS}} as an unfilled token.

1. ⚠️ Bug: {{ARGS}} flagged as unfilled token but is native Just syntax
   Files: REQUIRES_INITIALISATION.md:42-49, Justfile:58-59, .machine_readable/contractiles/Justfile

   REQUIRES_INITIALISATION.md lists `{{ARGS}}` as a substitution token still needing a value, but `{{ARGS}}` is Just's own positional-argument interpolation for the `invariant-path *ARGS:` recipe (`./scripts/invariant-path.sh {{ARGS}}`), not an estate placeholder. This is a false positive: a reader/agent instructed to 'resolve' it would break the recipe, and because this interpolation never disappears from the tree, the file's own deletion criterion ('delete only when no token below remains anywhere in the tree') can never be met — the gate never goes green, defeating the file's purpose. Exclude Just's `{{ARGS}}`/`{{ARG}}` recipe interpolations from the token scan (they are always paired with a `*ARGS`/parameter declaration) and regenerate the file; here it should report zero outstanding tokens.

2. ⚠️ Bug: Issues/registry URLs hardcoded to bag-of-actions, not remote slug
   Files: Justfile:704, .machine_readable/contractiles/Justfile:604

   The diff replaced `{{OWNER}}/{{REPO}}` with the literal `hyperpolymath/bag-of-actions` (issues link and container-matrix registry), but the actual git remote for this repository is `github.com/hyperpolymath/continuation-mesh`. The PR states identity was derived from the git remote, yet the value substituted is the internal project name, not the remote slug. If `hyperpolymath/bag-of-actions` is not a rename-aliased repo, `just help-me` will send bug reporters to a 404. Verify the canonical slug and substitute `continuation-mesh` (or confirm the GitHub rename redirect exists) so the issue link resolves.

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]

⚠️ Bug: {{ARGS}} flagged as unfilled token but is native Just syntax

REQUIRES_INITIALISATION.md lists {{ARGS}} as a substitution token still needing a value, but {{ARGS}} is Just's own positional-argument interpolation for the invariant-path *ARGS: recipe (./scripts/invariant-path.sh {{ARGS}}), not an estate placeholder. This is a false positive: a reader/agent instructed to 'resolve' it would break the recipe, and because this interpolation never disappears from the tree, the file's own deletion criterion ('delete only when no token below remains anywhere in the tree') can never be met — the gate never goes green, defeating the file's purpose. Exclude Just's {{ARGS}}/{{ARG}} recipe interpolations from the token scan (they are always paired with a *ARGS/parameter declaration) and regenerate the file; here it should report zero outstanding tokens.

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

[gitar-bot]

⚠️ Bug: Issues/registry URLs hardcoded to bag-of-actions, not remote slug

The diff replaced {{OWNER}}/{{REPO}} with the literal hyperpolymath/bag-of-actions (issues link and container-matrix registry), but the actual git remote for this repository is github.com/hyperpolymath/continuation-mesh. The PR states identity was derived from the git remote, yet the value substituted is the internal project name, not the remote slug. If hyperpolymath/bag-of-actions is not a rename-aliased repo, just help-me will send bug reporters to a 404. Verify the canonical slug and substitute continuation-mesh (or confirm the GitHub rename redirect exists) so the issue link resolves.

_{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.}

[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.