chore: fill derivable placeholders, drop false ARCHITECTURE, surface the rest - #25
Conversation
…the rest
Estate top-up pass. Three separate things, none of which invents a value.
FILLED — every token with a single mechanical answer: OWNER, REPO, FORGE,
PROJECT, PACKAGE_NAME, PROJECT_NAME, AUTHOR, AUTHOR_EMAIL, CONDUCT_EMAIL,
AUTHOR_FIRST/LAST/INITIALS, CURRENT_YEAR, CURRENT_DATE, DATE, MAIN_BRANCH.
Identity comes from the git remote, dates from the clock, project name from the
README H1 where there is one.
Deliberately NOT filled, because more than one defensible answer exists and a
confident wrong value is worse than a visible gap: SECURITY_EMAIL (two competing
addresses are in use across the estate), RESPONSE_TIME, CONDUCT_TEAM (which
substitutes into "a {{CONDUCT_TEAM}} member", not English), WEBSITE,
PROJECT_DESCRIPTION, LANG_STACK.
DELETED — ARCHITECTURE.md, where it is byte-identical to the 346-copy estate
boilerplate (blob 607e3d8). Those 33 lines describe a src/ tests/ docs/
scripts/ config/ tree that this repo does not have, so the file is not merely
uninformative, it is wrong. Genuinely written ARCHITECTURE files are matched by
hash and left alone. No file beats a confidently false one.
CODEOWNERS — rewritten to the solo form mandated by
hyperpolymath/standards CODEOWNERS-POLICY.adoc Rule 1, which forbids a catch-all
line where the only owner is the sole maintainer. The estate's own
templates/CODEOWNERS contradicts that policy; the policy is versioned, dated and
resolves standards#55, so it wins. Files naming a genuine co-owner are Rule 2
and are untouched. Note @hyperpolymath and @metadatastician are the same person,
so a file naming the other account is a copy artifact that silently routed
review requests to the wrong account.
SURFACED — REQUIRES_INITIALISATION.md, and a priority action in
0-AI-MANIFEST.a2ml. Tokens that need a decision no script can make are left
visibly unfilled rather than faked or quietly deleted. The marker says what each
one is, which files it belongs in, why it was not done already, and that it must
be deleted only once the work is genuinely finished.
|
![gitar-bot[bot]](https://avatars.githubusercontent.com/in/827041?s=60&v=4){kind=small}
| Replace all {{PLACEHOLDER}} values: | ||
| {{PROJECT_NAME}} - Your project name | ||
| {{OWNER}} - GitHub/GitLab username or org | ||
| {{REPO}} - Repository name | ||
| {{CONDUCT_EMAIL}} - Email for conduct reports | ||
| ReScript Ecosystem — Donation Staging Wrapper - Your project name | ||
| hyperpolymath - GitHub/GitLab username or org | ||
| rescript-ecosystem - Repository name | ||
| j.d.a.jewell@open.ac.uk - Email for conduct reports | ||
| {{CONDUCT_TEAM}} - Name of conduct team/committee | ||
| {{RESPONSE_TIME}} - Initial response SLA (e.g., 48 hours) | ||
| {{CURRENT_YEAR}} - Current year | ||
| 2026 - Current year |
There was a problem hiding this comment.
💡 Quality: Substitution corrupted the template-instruction legend
The top-up pass replaced the placeholder tokens inside the 'Replace all {{PLACEHOLDER}} values' legend itself, so the mapping now reads e.g. 'ReScript Ecosystem — Donation Staging Wrapper - Your project name' and 'hyperpolymath - GitHub/GitLab username or org'. The legend can no longer be used to identify which token corresponds to which value, and it sits alongside the still-unfilled {{CONDUCT_TEAM}}/{{RESPONSE_TIME}} lines. Since the block is meant to be deleted before publishing, prefer leaving the legend tokens intact (or deleting the whole instruction block) rather than substituting into label text.
Was this helpful? React with 👍 / 👎
| {{~ Aditionally delete this line and fill out the template below ~}} | ||
|
|
||
| # {{PROJECT}} ABI/FFI Documentation | ||
| # RESCRIPT_ECOSYSTEM ABI/FFI Documentation |
There was a problem hiding this comment.
💡 Quality: ABI-FFI-README project name inconsistent with rest of estate
{{PROJECT}} was filled as 'RESCRIPT_ECOSYSTEM' (upper-snake repo slug) whereas the human project name used elsewhere (e.g. CODE_OF_CONDUCT.md) is 'ReScript Ecosystem — Donation Staging Wrapper'. The heading '# RESCRIPT_ECOSYSTEM ABI/FFI Documentation' reads oddly and the Idris example 'import RESCRIPT_ECOSYSTEM.ABI.Foreign' does not match a conventional module namespace. Consider using the proper project/module name for consistency.
Was this helpful? React with 👍 / 👎
|
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. Code Review 👍 Approved with suggestions 0 resolved / 2 findingsAutomated estate top-up pass filling mechanical placeholders and removing boilerplates. Consider restoring the template-instruction legend tokens and aligning the project name with the rest of the estate.
💡 Quality: Substitution corrupted the template-instruction legend📄 bridge-web-rescript/CODE_OF_CONDUCT.md:7-14 The top-up pass replaced the placeholder tokens inside the 'Replace all {{PLACEHOLDER}} values' legend itself, so the mapping now reads e.g. 'ReScript Ecosystem — Donation Staging Wrapper - Your project name' and 'hyperpolymath - GitHub/GitLab username or org'. The legend can no longer be used to identify which token corresponds to which value, and it sits alongside the still-unfilled {{CONDUCT_TEAM}}/{{RESPONSE_TIME}} lines. Since the block is meant to be deleted before publishing, prefer leaving the legend tokens intact (or deleting the whole instruction block) rather than substituting into label text. 💡 Quality: ABI-FFI-README project name inconsistent with rest of estate📄 bridge-web-rescript/ABI-FFI-README.md:3 📄 bridge-web-rescript/ABI-FFI-README.md:250 {{PROJECT}} was filled as 'RESCRIPT_ECOSYSTEM' (upper-snake repo slug) whereas the human project name used elsewhere (e.g. CODE_OF_CONDUCT.md) is 'ReScript Ecosystem — Donation Staging Wrapper'. The heading '# RESCRIPT_ECOSYSTEM ABI/FFI Documentation' reads oddly and the Idris example 'import RESCRIPT_ECOSYSTEM.ABI.Foreign' does not match a conventional module namespace. Consider using the proper project/module name for consistency. 🤖 Prompt for agentsOptionsDisplay: compact → Showing less information. Comment with these commands to change the behavior for this request:
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 |
There was a problem hiding this comment.
Configure merge blocking · Maintainers can dismiss this review.
|
|
1 participant
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.mdwhere it is byte-identical to the 346-copy estate boilerplate (blob607e3d8c). Those 33 lines describe asrc/ 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.adocRule 1, which forbids a catch-all where the only owner is the sole maintainer.templates/CODEOWNERScontradicts that policy; the policy is versioned, dated and resolvesstandards#55, so it wins. Genuine co-owners (Rule 2) are untouched.Surfaced —
REQUIRES_INITIALISATION.mdplus a priority action in0-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