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

.github/CODEOWNERS

@@ -1,14 +1,4 @@
 # SPDX-License-Identifier: MPL-2.0
-# CODEOWNERS - Define code review assignments
-# See: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
-#
-# Replace hyperpolymath with your GitHub username or team
-
-# Default owners for everything
-* @hyperpolymath
-
-# Security-sensitive files require explicit review
-SECURITY.md @hyperpolymath
-.github/workflows/ @hyperpolymath
-Trustfile.a2ml @hyperpolymath
-.machine_readable/ @hyperpolymath
+# Solo-maintained hyperpolymath repo: no owner lines by policy.
+# See hyperpolymath/standards CODEOWNERS-POLICY.adoc (Rule 1).
+# Sole-maintainer review is moot; SPDX headers carry attribution.

.github/CODE_OF_CONDUCT.md

@@ -8,7 +8,7 @@ Replace all values:
  Patch Bridge - Your project name
  hyperpolymath - GitHub/GitLab username or org
  patch-bridge - Repository name
-{{CONDUCT_EMAIL}} - Email for conduct reports
+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)
  2026 - Current year
@@ -136,7 +136,7 @@ If you experience or witness unacceptable behaviour, or have any other concerns,
 
 | Method | Details | Best For |
 |--------|---------|----------|
-| **Email** | {{CONDUCT_EMAIL}} | Detailed reports, sensitive matters |
+| **Email** | j.d.a.jewell@open.ac.uk | Detailed reports, sensitive matters |
 | **Private Message** | Contact any maintainer directly | Quick questions, minor issues |
 | **Anonymous Form** | [Link to form if available] | When you need anonymity |
 
@@ -231,7 +231,7 @@ For contributors with elevated access (Perimeter 2 or 1):
 If you believe an enforcement decision was made in error:
 
 1. **Wait 7 days** after the decision (cooling-off period)
-2. **Email** {{CONDUCT_EMAIL}} with subject line "Appeal: [Original Report ID]"
+2. **Email** j.d.a.jewell@open.ac.uk with subject line "Appeal: [Original Report ID]"
 3. **Explain** why you believe the decision should be reconsidered
 4. **Provide** any new information not previously available
 
@@ -310,8 +310,8 @@ We thank these communities for their leadership in creating welcoming spaces.
 
 If you have questions about this Code of Conduct:
 
-- Open a [Discussion](https://{{FORGE}}/hyperpolymath/patch-bridge/discussions) (for general questions)
-- Email {{CONDUCT_EMAIL}} (for private questions)
+- Open a [Discussion](https://github.com/hyperpolymath/patch-bridge/discussions) (for general questions)
+- Email j.d.a.jewell@open.ac.uk (for private questions)
 - Contact any maintainer directly
 
 ---

.github/CONTRIBUTING.md

@@ -1,5 +1,5 @@
 # Clone the repository
-git clone https://{{FORGE}}/hyperpolymath/patch-bridge.git
+git clone https://github.com/hyperpolymath/patch-bridge.git
 cd patch-bridge
 
 # Using Nix (recommended for reproducibility)
@@ -58,7 +58,7 @@ patch-bridge/
 
 **Before reporting**:
 1. Search existing issues
-2. Check if it's already fixed in `{{MAIN_BRANCH}}`
+2. Check if it's already fixed in `main`
 3. Determine which perimeter the bug affects
 
 **When reporting**:
@@ -91,10 +91,10 @@ Use the [feature request template](.github/ISSUE_TEMPLATE/feature_request.md) an
 
 Look for issues labelled:
 
-- [`good first issue`](https://{{FORGE}}/hyperpolymath/patch-bridge/labels/good%20first%20issue) — Simple Perimeter 3 tasks
-- [`help wanted`](https://{{FORGE}}/hyperpolymath/patch-bridge/labels/help%20wanted) — Community help needed
-- [`documentation`](https://{{FORGE}}/hyperpolymath/patch-bridge/labels/documentation) — Docs improvements
-- [`perimeter-3`](https://{{FORGE}}/hyperpolymath/patch-bridge/labels/perimeter-3) — Community sandbox scope
+- [`good first issue`](https://github.com/hyperpolymath/patch-bridge/labels/good%20first%20issue) — Simple Perimeter 3 tasks
+- [`help wanted`](https://github.com/hyperpolymath/patch-bridge/labels/help%20wanted) — Community help needed
+- [`documentation`](https://github.com/hyperpolymath/patch-bridge/labels/documentation) — Docs improvements
+- [`perimeter-3`](https://github.com/hyperpolymath/patch-bridge/labels/perimeter-3) — Community sandbox scope
 
 ---
 

.well-known/security.txt

@@ -6,6 +6,6 @@ Contact: mailto:{{SECURITY_EMAIL}}
 Expires: 2026-12-31T23:59:59.000Z
 Encryption: {{PGP_KEY_URL}}
 Preferred-Languages: en
-Canonical: https://{{FORGE}}/hyperpolymath/patch-bridge/.well-known/security.txt
-Policy: https://{{FORGE}}/hyperpolymath/patch-bridge/blob/main/SECURITY.md
+Canonical: https://github.com/hyperpolymath/patch-bridge/.well-known/security.txt
+Policy: https://github.com/hyperpolymath/patch-bridge/blob/main/SECURITY.md
 Hiring: https://{{WEBSITE}}/careers

0-AI-MANIFEST.a2ml

@@ -44,3 +44,20 @@ Canonical project metadata belongs under `.machine_readable/`.
 1. Read this file.
 2. Read `.machine_readable/STATE.a2ml` and `.machine_readable/6a2/STATE.a2ml`.
 3. Check the current audit report before modifying claims or release posture.
+
+<!-- BEGIN requires-initialisation -->
+
+## PRIORITY ACTION — this repository is not fully initialised
+
+35 substitution token(s) still have no value. **Read
+`REQUIRES_INITIALISATION.md` in the repository root before doing anything
+else here** — it lists every outstanding token, what it means, and which
+files it belongs in.
+
+Do not fabricate values for them, and do not delete the sections that
+contain them to quiet a gate. They are unfilled because they need a
+decision, not because they were overlooked. Resolve what you legitimately
+can, leave the rest, and delete `REQUIRES_INITIALISATION.md` only when
+nothing outstanding remains.
+
+<!-- END requires-initialisation -->

QUICKSTART-MAINTAINER.adoc

@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: CC-BY-SA-4.0
 // Template: QUICKSTART-MAINTAINER.adoc — packaging, deploying, and maintaining
-// Replace rsr-template-repo, {{PACKAGE_NAME}}, {{DEPS}} with actuals
+// Replace rsr-template-repo, patch-bridge, {{DEPS}} with actuals
 = rsr-template-repo — Quick Start for Platform Maintainers
 :toc:
 :toclevels: 2
@@ -65,10 +65,10 @@ Files installed:
 | `$PREFIX/bin/`
 | Executables
 
-| `$PREFIX/share/{{PACKAGE_NAME}}/`
+| `$PREFIX/share/patch-bridge/`
 | Data files, assets
 
-| `$PREFIX/share/doc/{{PACKAGE_NAME}}/`
+| `$PREFIX/share/doc/patch-bridge/`
 | Documentation
 
 | `$PREFIX/share/applications/`
@@ -80,9 +80,9 @@ Files installed:
 
 == Configuration
 
-Default config location: `$XDG_CONFIG_HOME/{{PACKAGE_NAME}}/config.toml`
+Default config location: `$XDG_CONFIG_HOME/patch-bridge/config.toml`
 
-Fallback: `$HOME/.config/{{PACKAGE_NAME}}/config.toml`
+Fallback: `$HOME/.config/patch-bridge/config.toml`
 
 == Health Checks
 
@@ -102,7 +102,7 @@ just build-release
 just install --prefix=/usr/local
 ----
 
-Or via OPSM: `opsm update {{PACKAGE_NAME}}`
+Or via OPSM: `opsm update patch-bridge`
 
 == Security Notes
 
@@ -117,8 +117,8 @@ For deploying multiple instances (e.g., different users or tenants):
 
 [source,bash]
 ----
-just install --prefix=/opt/{{PACKAGE_NAME}}-instance1 --config=/etc/{{PACKAGE_NAME}}/instance1.toml
-just install --prefix=/opt/{{PACKAGE_NAME}}-instance2 --config=/etc/{{PACKAGE_NAME}}/instance2.toml
+just install --prefix=/opt/patch-bridge-instance1 --config=/etc/patch-bridge/instance1.toml
+just install --prefix=/opt/patch-bridge-instance2 --config=/etc/patch-bridge/instance2.toml
 ----
 
 Each instance has isolated config, data, and logs.