docs(archive): preserve discussions for merged PRs

.gitignore

@@ -208,8 +208,10 @@ result-*
 
 # Per-machine NixOS hardware config — generated by `nixos-generate-config`
 # on each target machine. Committed under
-# infra/nixos/hosts/<host>/hardware-configuration.nix WHEN the host's
+# infra/nixos/hosts/<host>/hardware-configuration.nix
+tools/alignment/out/ WHEN the host's
 # hardware is known and shouldn't drift; ignored at top-level so a
 # `nixos-generate-config` run in the repo root doesn't accidentally
 # pollute the working tree.
 /hardware-configuration.nix
+tools/alignment/out/

docs/pr-discussions/PR-4965-backlog-b-0726-reticulum-throughout-cluster-nodes-edge-devic.md

@@ -0,0 +1,27 @@
+---
+pr_number: 4965
+title: "backlog(B-0726): Reticulum throughout \u2014 cluster nodes + edge devices on one mesh"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-25T17:44:56Z"
+merged_at: "2026-05-25T17:47:00Z"
+closed_at: "2026-05-25T17:47:00Z"
+head_ref: "backlog/b0726-reticulum-throughout-cluster-and-edge-2026-05-25-c2"
+base_ref: "main"
+archived_at: "2026-05-25T23:44:56Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4965: backlog(B-0726): Reticulum throughout — cluster nodes + edge devices on one mesh
+
+## PR description
+
+Files Aaron's *'i'm thinking it will require reticiulum at the edge and in cluster'* — Reticulum runs in the cluster as a composing substrate alongside K8s, not partitioned by network tier. Cluster nodes speak Reticulum natively; workloads addressable via both Cilium (intra-cluster) and Reticulum (cross-substrate identity-routing).
+
+Composes with B-0289 Green Lantern (already-in-progress edge substrate); PR #4930 hat-system (Reticulum identities can be hat-bound with succession semantics); SPIRE (identity-issuer pattern); m-acc / multi-oracle / NCI / 5-always-active-disciplines.
+
+Includes 4-tier-federation cross-ref to B-0727. 6 open design-pass questions. P2 because needs design pass; becomes P1 when first edge-device-needs-cluster-mesh-reachability deployment surfaces.
+
+Single file (+ index regen) — research-grade architecture, no implementation in this PR.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)

docs/pr-discussions/PR-4966-backlog-b-0727-federated-peer-mesh-5-resource-profiles-weigh.md

@@ -0,0 +1,73 @@
+---
+pr_number: 4966
+title: "backlog(B-0727): federated peer mesh \u2014 5 resource profiles, weight-free routing, NO hierarchy"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-25T17:44:58Z"
+merged_at: "2026-05-25T17:47:25Z"
+closed_at: "2026-05-25T17:47:25Z"
+head_ref: "backlog/b0727-federated-peer-mesh-weight-free-2026-05-25-c2"
+base_ref: "main"
+archived_at: "2026-05-25T23:44:56Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4966: backlog(B-0727): federated peer mesh — 5 resource profiles, weight-free routing, NO hierarchy
+
+## PR description
+
+Files Aaron's federated topology + the LOAD-BEARING weight-free correction:
+
+  > 'imagine cloud/hub clusters then community clusters then home/business clusers then edge nodes with routing for weaker edge nodes'
+  > 'and that's not a hierarchy it's weight free routing cloud/hub nodes don't get to hog net neutrality'
+
+The 5 categories (cloud/hub, community, home/business, edge, leaf) are RESOURCE PROFILES, not authority tiers. Cloud/hub has MORE RESOURCES but NOT MORE AUTHORITY. Routing is identity-based not rank-based. Net neutrality is a SUBSTRATE PROPERTY enforced at protocol layer. Stronger peers route for weaker leaves BY VOLUNTARY CONTRIBUTION (NCI-revocable), not by hierarchy mandate.
+
+Composes with all 5 always-active substrate-engineering disciplines (scale-free + lock-free + weight-free [primary] + DST + DV2.0), plus framework rules (NCI floor at routing, additive-not-zero-sum, m-acc multi-oracle, default-to-both, tonal-momentum resistance).
+
+Internet analogy table shows where this consciously DIVERGES — Internet got routing protocol right (BGP) but authority model wrong (tier-1 + DNS root + CA hierarchy); this federation gets weight-free authority.
+
+Anti-extractive guarantee: surveillance / censorship / transit-toll detection via web-of-trust reputation degradation.
+
+P3 because research-grade architecture; needs design pass + first multi-peer deployment.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @chatgpt-codex-connector (2026-05-25T17:47:43Z)
+
+
+### 💡 Codex Review
+
+Here are some automated review suggestions for this pull request.
+
+**Reviewed commit:** `f8a52ac15e`
+
+
+<details> <summary>ℹ️ About Codex in GitHub</summary>
+<br/>
+
+[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you
+- Open a pull request for review
+- Mark a draft as ready
+- Comment "@codex review".
+
+If Codex has suggestions, it will comment; otherwise it will react with 👍.
+
+
+Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
+
+</details>
+
+## Review threads
+
+### Thread 1: docs/backlog/P3/B-0727-federated-4-tier-cluster-topology-cloud-community-home-business-edge-with-routing-for-weaker-leaves-2026-05-25.md:16 (unresolved)
+
+**@chatgpt-codex-connector** (2026-05-25T17:47:44Z):
+
+**<sub><sub>![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)</sub></sub>  Fix dangling composes_with references**
+
+This row adds `composes_with` entries that do not resolve to tracked targets (`docs/backlog/P2/B-0726-...` and `full-ai-cluster/k8s/applications/argocd/` are both absent in this tree), which leaves the backlog graph with broken edges and makes cross-row traceability/tooling unreliable when following prerequisites. Please point these to existing paths (or land the referenced row first) so the metadata remains navigable and machine-consumable.
+
+Useful? React with 👍 / 👎.

docs/pr-discussions/PR-4968-docs-require-work-anchors-for-organization-discussions.md

@@ -0,0 +1,102 @@
+---
+pr_number: 4968
+title: "docs: require work anchors for organization discussions"
+author: "maximdolphin"
+state: "MERGED"
+created_at: "2026-05-25T18:12:51Z"
+merged_at: "2026-05-25T18:15:44Z"
+closed_at: "2026-05-25T18:15:44Z"
+head_ref: "codex/discussion-work-anchors"
+base_ref: "main"
+archived_at: "2026-05-25T23:44:56Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4968: docs: require work anchors for organization discussions
+
+## PR description
+
+## Summary
+
+- Adds the Agent-Native Knowledge Graph and Retrieval doc as the agent-first context layer for tasks, discussions, decisions, meetings, docs, artifacts, runs, memories, and evidence.
+- Makes discussion anchoring a hard Organization invariant: meetings, one-on-ones, team chats, TPM/executive meetings, broadcasts, votes, reports, and review comments must reference a work item or scoped organizational artifact before opening.
+- Propagates `validate_discussion_anchor`, `discussion_anchors`, and anchor-aware behavior through MCP tools, the Work OS, UI, actors, scheduled jobs, readiness checks, and runtime architecture docs.
+
+## Validation
+
+- `git diff --check HEAD~1 HEAD`
+- `rg -n "AGENT_NATIVE_KNOWLEDGE_GRAPH|Discussion Anchor|validate_discussion_anchor|No discussion may be unanchored" agentic-organization/docs`
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-25T18:15:47Z)
+
+## Pull request overview
+
+This PR strengthens the “discussion anchoring” invariant across the Agentic Organization design docs and introduces a new Agent-Native Knowledge Graph/Retrieval document as the context layer tying work items to discussions, decisions, evidence, and runs.
+
+**Changes:**
+- Adds `AGENT_NATIVE_KNOWLEDGE_GRAPH.md` describing a typed graph schema, retrieval contracts, context packs, and `validate_discussion_anchor`.
+- Propagates “no unanchored discussions” requirements through OS, UI/observability, runtime architecture, build plan, and readiness checklist docs.
+- Updates tool bundles and actor/runtime descriptions to include discussion anchor validation and tracking.
+
+### Reviewed changes
+
+Copilot reviewed 13 out of 13 changed files in this pull request and generated 4 comments.
+
+<details>
+<summary>Show a summary per file</summary>
+
+| File | Description |
+| ---- | ----------- |
+| agentic-organization/docs/WORK_AND_RELEASE_MANAGEMENT_OS.md | Adds anchor validation into the signal model and guardrails. |
+| agentic-organization/docs/UI_AND_OBSERVABILITY_CONCEPTS.md | Requires an anchor selector before opening discussions; records anchor in meeting UI metadata. |
+| agentic-organization/docs/RUNTIME_TECH_AND_PACKAGE_STRATEGY.md | Extends actor responsibilities to include anchor state and adds anchor to runtime context. |
+| agentic-organization/docs/README.md | Adds the new Knowledge Graph/Retrieval doc to the canonical doc list. |
+| agentic-organization/docs/ORGANIZATION_RUNTIME_ARCHITECTURE.md | Introduces an explicit Discussion Anchor Policy and updates meeting/chat requirements. |
+| agentic-organization/docs/ORGANIZATION_LAYER_BUILD_PLAN.md | Adds “discussion anchors” as a first-class schema/service concern and as workspace context. |
+| agentic-organization/docs/IMPLEMENTATION_READINESS_CHECKLIST.md | Adds discussion anchors + Knowledge Graph/Retrieval V0 decisions and preflight tools. |
+| agentic-organization/docs/IMPLEMENTATION_CONCEPTS.md | Adds anchor enforcement requirements to meeting concepts and open preflight steps. |
+| agentic-organization/docs/DEPARTMENT_HAT_TOOL_INVENTORY.md | Adds `validate_discussion_anchor` into tool bundles. |
+| agentic-organization/docs/ANTI_STALL_PRIORITY_RUNTIME.md | Requires anchors for prioritization meetings and votes. |
+| agentic-organization/docs/AMBIGUOUS_REQUIREMENT_LIFECYCLE.md | Anchors customer interview threads to intake/work items. |
+| agentic-organization/docs/ALWAYS_ON_ORCHESTRATION_RUNTIME.md | Requires scheduled jobs to supply discussion anchors when opening comms artifacts. |
+| agentic-organization/docs/AGENT_NATIVE_KNOWLEDGE_GRAPH.md | New: defines graph node/edge schema, retrieval/context-pack contracts, and anchoring/tooling expectations. |
+</details>
+
+## Review threads
+
+### Thread 1: agentic-organization/docs/AGENT_NATIVE_KNOWLEDGE_GRAPH.md:191 (unresolved)
+
+**@copilot-pull-request-reviewer** (2026-05-25T18:15:46Z):
+
+The example edge directions here conflict with the `discussed_in` contract just above (which says `discussed_in` is "subject -> conversation"). If `Meeting` is the conversation node, the source/target should be flipped (e.g., `Initiative`/`Task` -> `discussed_in` -> `Meeting`) or the edge kind renamed to match the intended direction.
+
+### Thread 2: agentic-organization/docs/AGENT_NATIVE_KNOWLEDGE_GRAPH.md:195 (unresolved)
+
+**@copilot-pull-request-reviewer** (2026-05-25T18:15:46Z):
+
+This example uses edge labels (`produced`, `cited`, `recorded_by`) that are not present in the declared `EdgeKind` union (which has `produced_by` and `cites`, and no `recorded_by`). To avoid schema drift, align the example with the enumerated edge kinds (or update `EdgeKind`/the edge table to include the missing kinds).
+
+### Thread 3: agentic-organization/docs/AGENT_NATIVE_KNOWLEDGE_GRAPH.md:216 (unresolved)
+
+**@copilot-pull-request-reviewer** (2026-05-25T18:15:46Z):
+
+This section is titled "Discussion Anchor Invariant" and defines a `DiscussionAnchor` type, but the prose uses the term "work anchor". Consider standardizing on one term (or explicitly defining "work anchor" as an alias of "discussion anchor") so the docs, types, and tool names (`validate_discussion_anchor`) stay consistent.
+
+### Thread 4: agentic-organization/docs/ORGANIZATION_RUNTIME_ARCHITECTURE.md:1738 (unresolved)
+
+**@copilot-pull-request-reviewer** (2026-05-25T18:15:47Z):
+
+In this section the list uses both "context gap" (no hyphen) and "context-gap" (hyphenated). Please standardize the spelling to one form to keep anchor types/search terms consistent across the docs (especially since the type uses `context_gap`).
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-25T18:12:56Z)
+
+Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
+Credits must be used to enable repository wide code reviews.
+
+### @maximdolphin (2026-05-25T18:56:10Z)
+
+Follow-up added in `059f57bff`: documented the agent work rhythm model. Hats now carry schedule templates, prompt-flow availability, review/red-team blocks, reflection/memory-maintenance blocks, and bounded free time. The docs also add a prompt-flow registry model with reusable phases, deterministic MCP-driven execution, reviewer gates, graph ingestion, capability-expansion lifecycle, UI surfaces, schedule/prompt-flow signals, and v0 readiness contracts.

docs/pr-discussions/PR-4969-shard-1808z-pr-4953-cold-boot-triage-peer-rescue-already-lan.md

@@ -0,0 +1,40 @@
+---
+pr_number: 4969
+title: "shard(1808Z): PR #4953 cold-boot triage \u2014 peer rescue already landed; empirical comment + reopen"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-25T18:18:43Z"
+merged_at: "2026-05-25T18:21:19Z"
+closed_at: "2026-05-25T18:21:19Z"
+head_ref: "otto-cli/1808z-shard-2026-05-25"
+base_ref: "main"
+archived_at: "2026-05-25T23:44:56Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #4969: shard(1808Z): PR #4953 cold-boot triage — peer rescue already landed; empirical comment + reopen
+
+## PR description
+
+## Summary
+
+Tick shard for Otto-CLI autonomous-loop fresh cold-boot at 2026-05-25T18:08Z. Documents PR #4953 (k3d ai-cluster) closed-PR triage where peer Otto rescue had already landed BEFORE Aaron's close.
+
+## Key empirical finding
+
+`gh api .../commits/4578fab7d/check-runs` shows `lint (markdownlint)` completed **success** at 16:49:47Z — **41 seconds BEFORE** Aaron's close at 16:50:28Z. PR HEAD at close was already `4578fab7d` (post-fix). Substrate-honest disposition: empirical-evidence comment + reopen per Aaron's explicit "before re-opening" instruction.
+
+## Composes with
+
+- [`honor-those-that-came-before.md`](../docs/../../.claude/rules/honor-those-that-came-before.md) — verifying peer substrate IS the honor (extended from orphaned-branch triage to closed-PR triage)
+- [`verify-before-deferring.md`](../docs/../../.claude/rules/verify-before-deferring.md) — verified peer commits on origin before pushing own fix
+- [`holding-without-named-dependency-is-standing-by-failure.md`](../docs/../../.claude/rules/holding-without-named-dependency-is-standing-by-failure.md) — concrete-artifact counter reset (named dep PR #4953 + lint ask)
+
+## Test plan
+
+- [x] markdownlint passes on the new shard (`bunx markdownlint-cli2`)
+- [x] ls-tree canary: 60 entries pre + post both commits, +1 file each (no corruption)
+- [x] Isolated worktree off `origin/main` (6062549c6)
+- [ ] CI green; auto-merge fires
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)