Archive prefer-triad-project-shape: 5.6 realized by openRepoProject #8 → d7f6b0ee, packet closed

[brettheap]

Lane: codeXfactory-5

Archives the ratified OpenSpec change prefer-triad-project-shape and promotes its delta into openspec/specs/project-repo-schema/spec.md. Task 5.6 is now realized by openRepoProject #8 → d7f6b0ee, so every tasks.md § 5 surface has merged, green realization evidence.

Authority (Brett Heap, verbatim)

• The archive word. The STANDING word was "archive prefer-triad-project-shape when 5.6 lands", given at 2026-10-07T10:20:48Z and RULED on the lane register at 2026-10-07T10:21:23Z. Its recorded reading has four parts:
  • The trigger is task 5.6's realization merging with green checks. That realization is new-project creation offering the Triad first, owned by lane openRepoProject-1 through openRepoProject#3 and its OpenSpec change prefer-triad-in-project-new.
  • codeXfactory-5 then records the 5.6 tick citing that merge sha.
  • It archives the change through openxFactory's archive wrapper, promoting the delta into openspec/specs/project-repo-schema.
  • It does so as one archive PR, landing by merge commit under a Rule 6 window on this word, with no further word needed.
• The trigger is met. openRepoProject PR Add dogfood content migration plan #8 merged at 2026-10-08T23:43:48Z as d7f6b0eeebf3370be13de87193f397592ebd73a9.
  • At its head f8dde973, all eight test runs and SonarCloud succeeded, and Sourcery was skipped.
  • On main at d7f6b0ee, all four test jobs succeeded and SonarCloud was neutral.
  • These were re-verified from the check runs.
• The owner-box ruling. At 2026-10-08T20:04:44Z Brett Heap selected, verbatim, "Yes, here and prefer-triad (Recommended)". It was RULED on the lane register at 2026-10-08T20:05:35Z. The option text: tick the owner boxes as discharged by word, each citing his word and its time, as Archive state-header-window-budget on landing (Brett Heap's word "archive 921", 2026-09-11T10:21:39Z) #953 did; owner boxes whose acts he recorded get the same treatment when prefer-triad-project-shape is archived; and any box without a recorded word stops that archive.

Owner-box discharges

Every owner box has a recorded word. Each tick records Brett Heap's act, not the agent's.

box	word (verbatim)	time (UTC)	where recorded
1.1 the reading	"ratify 1249 as recommended"	2026-10-06T16:02:16Z	#1249 RATIFIED comment 6020300563; review/ratification-2026-10-06.md; lane register RULED 16:03:51Z
1.2 OQ-1	same word ("as recommended": single-repository.yaml at the root, schema owned by openRepoShape)	2026-10-06T16:02:16Z	as 1.1, and the box's own RULED note
1.3 OQ-2	same word (no class-guessing)	2026-10-06T16:02:16Z	as 1.1, and the box's own RULED note
1.4 OQ-3	same word (no block on the ownership requirement)	2026-10-06T16:02:16Z	as 1.1, and the box's own RULED note
1.5 merge	"merge 1249"	2026-10-06T17:31:10Z (the session transcript's timestamp of the word)	#1249 LANDING comment 6021840005 (17:33:23Z) and LANDED comment 6021851396 (17:34:04Z), landed as e63809650d39586134c4ec4fdb6e9effc87a7860; lane register LANDING 17:33:13Z and LANDED 17:33:58Z

Task 4.3 facts (verified from #1249's check runs and review record)

• Checks. At the final head 020f2e4f, all 16 check runs succeeded except Sourcery review, which was skipped. All eight required contexts passed, and so did merge-master-approval and SonarCloud.
• No Codex review was delivered. @codex review was requested at 2026-10-06T14:24:19Z (comment 6018384460). The Codex connector replied at 14:24:31Z (comment 6018388372) with a usage-limit notice.
• Sourcery posted a review-budget notice (14:25:57Z) and a reviewer's guide (14:26:16Z, comment 6018422124). Neither carries a finding.
• The review record has 0 reviews, 0 review threads and 0 pending review requests, so no thread is left unanswered.
• The basis for the tick is the green checks and the absence of any unanswered thread. The note states plainly that no Codex review was delivered.

Task 5.6 and the 6.1 archive record

• 5.6 is realized by openRepoProject Add dogfood content migration plan #8 → d7f6b0ee, owned by lane openRepoProject-1 (the PR body's Lane: line).

  • project new asks one question with the Triad listed first as the default, and asks no reason for a single repository.
  • The question creates nothing. openRepoShape's typed confirmation and Type yes remain the only confirmations, so no repository is created that the person has not confirmed.
  • It realizes openRepoProject's own OpenSpec change prefer-triad-in-project-new (ratified "ratify 5", PR Add install repo submodule decision #5 → ca4c6152), whose tasks 3.1 to 3.3 the tick cites. That change is still active in openRepoProject.
  • Disclosed: onp and new-project.sh reach the offer only once workBenches#145 moves lane project-command's pin, which still names a0407904.

• 6.1. design.md D9 names no record file, so the 6.1 note is the archive record. It cites each surface's merge and check runs:

  • openxFactory: prefer-triad-project-shape 5.1: the doctrine and register description restate the Triad as preferred, confers nothing #1254 → a2dc658d, prefer-triad-project-shape 5.3: advance the openRepoShape pin to 1a9fc537, the commit that realizes 5.2 #1260 → f335c077 and prefer-triad-project-shape 5.7: the estate inventory, a recommendation only #1255 → 0992369a;
  • openRepoShape: The publisher declares no pin on itself: unbreak doxBench's model routes #164 → 1a9fc537;
  • workBenches (outside the head): A dot is its document's checkbox, and a staged tile opens its packet #139 → 9fbe609c and A reload keeps your place #140 → d86ba59b;
  • openRepoProject (outside the head): Add dogfood content migration plan #8 → d7f6b0ee;
  • the private protocol source brettheap/new-workstation (outside the head), cited by sha and file name only: Release contract-v1.29 wheel, intent, and worker contracts #52 → e081c5ab and release: contract-v1.28 — the chat-turn request's active_document_path is nullable (G-1) #53 → cb411460. It runs no CI.

  The 5.1 and 5.3 notes name branch commits (31e0628a, 9af22071) that squash-landed as a2dc658d and f335c077. This is disclosed, and those notes are kept as written.

What moved

• Archive directory. openspec/changes/archive/2026-10-09-prefer-triad-project-shape/. The seven packet files move as pure renames (R100), and tasks.md then carries its closing ticks and the run record.

• The archive run. It went through the governed wrapper, TZ=UTC python3 scripts/proposal-support.py . archive prefer-triad-project-shape --yes, over the content-addressed @fission-ai/openspec@1.12.0 pin. It exited 0 and reported ORIGIN RETAINED … e63809650d39 and + 3 added, ~ 1 modified.

• Promoted onto project-repo-schema. Each block below is byte-identical between the archived delta and canon:

  • MODIFIED The project repository schema is elective and confers nothing (2,201 to 4,257 bytes);
  • ADDED A person starting work outside a Triad is advised once, and is never stopped for it;
  • ADDED A project's shape is never a review input;
  • ADDED The advisory is silent where the shape question is answered or does not arise.

  The other ten blocks are unmoved and keep their order. Canon is +175 −0.

• No block was brought forward. Canon's MODIFIED block is 2,201 bytes with sha256 prefix 9a3054ba7f7ccd09 both at the authoring base 92010d3e and at main. Archive correct-naming-families-count: doctrine #1270 → e83259b4, packet closed #1275 moved two other requirements only.

• README. The OpenSpec Records row moves from Active to Archived, and both of its links now name the archive path.

• Links repointed. Only those two README links pointed at the active path. docs/project-repo-schema.md:14 names the active path in code type inside a ratified Amended by: header. It is a historical record and is left as written, as Archive correct-naming-families-count: doctrine #1270 → e83259b4, packet closed #1275 left its :24 sibling.

• Ledger. tests/sequenced_after/corpus-ledger.yaml was re-seeded with --seed-ledger --moved-by '#1281', and exactly one row moved: prefer-triad-project-shape goes from active to archived, moved_by from #1249 to #1281, and moved_on from 2026-10-06 to 2026-10-09. Its class stays co-modifier.

• Main moved twice during the work, and was taken by merge both times, never rebase.

  • First to b80a4790 (Q-GRC-4: tick 4.3 — the intake register's records floored by name (codexFactory #534, re-pin #1277) #1280), merged in 4a04f51c. It touched no archive file.
  • Then, after this PR opened, to 564f565a (Archive refresh-install-repository-enumerations-opsxfactory-gateway: the sixth install repository promoted into the three enumerations; Purpose widened #1278, an overlapping archive), merged in 8f932992. README's Archived list conflicted at its head. The resolution keeps both entries byte for byte, this one (2026-10-09) first and Archive refresh-install-repository-enumerations-opsxfactory-gateway: the sixth install repository promoted into the three enumerations; Purpose widened #1278's (2026-10-08) after it.
  • The ledger auto-merged, and each archive moved its own row.
  • All six validators re-ran on 8f932992 and exit 0. The CLI reads 112 passed, 1 failed (113 items), with 46 active changes and the ledger consistent at 236 rows. The extra drop is Archive refresh-install-repository-enumerations-opsxfactory-gateway: the sixth install repository promoted into the three enumerations; Purpose widened #1278's own archive.

Validators, before (main b80a4790) and after (a769b25c, seeded)

Both sides ran in one scratch checkout named openxFactory, with the submodules CI initializes. Every validator exited 0 on both sides, and every difference is the archive's own effect.

validator	before	after	difference
validate-openspec-cli-pin.py --all --strict	114 passed, 1 failed (115 items)	113 passed, 1 failed (114 items)	This change left the item set. The failure is the accepted add-chain-attestation exception, the same on both sides. Three non-failing [INFO] ">500 characters" lines were added for the promoted ADDED requirements.
validate-sequenced-after.py .	48 active, 20 declaring	47 active, 20 declaring	This change left the active set. Both archive-date agreements pass.
… --ledger-diff	consistent (236 rows)	consistent (236 rows)	Totals went from 48/188 to 47/189, and active co-modified from 27 to 26. Before the seed it exited 1 on exactly this row.
validate-code-surface.py .	48 active, 32 repository lists, 11 identifiers	47, 31, 10	opensoft/openRepoShape was named only by this change.
validate-target-release.py .	48 active, 26 implemented	47, 25	This change left the active set.
doc-health.py --single-repo .	31 critical, 26 error, 69 warning, 19 info, 0 regressions	identical	Canon words rose by 1,986 (the promoted text). No finding names an archive file.

Overlapping open PRs (not touched)

• README Records block: amend-factory-mcp-conformance-auth-profile: auth block with an RS256 baseline, M5 narrowed to error codes, per-domain error vocabularies (ratified) #1274 (draft), 035 renew-resolved-council-protocol: specification, plan, tasks and analysis #1268 (draft) and Ratify realize-doc-health-direction-arc on Brett Heap's word (#656 6023375303) #1261. Archive refresh-install-repository-enumerations-opsxfactory-gateway: the sixth install repository promoted into the three enumerations; Purpose widened #1278 has since merged and is taken into this branch, above.
• tests/sequenced_after/corpus-ledger.yaml: amend-factory-mcp-conformance-auth-profile: auth block with an RS256 baseline, M5 narrowed to error codes, per-domain error vocabularies (ratified) #1274.
• No open PR touches openspec/specs/project-repo-schema/.

Lands by MERGE commit under Rule 6 on Brett Heap's standing word "archive prefer-triad-project-shape when 5.6 lands".

Copilot review not requested (Brett Heap, 2026-10-06).

🤖 Generated with Claude Code

Summary by Sourcery

Archive prefer-triad-project-shape and promote its ratified requirements into the canonical project repository schema.

New Features:

• Promote the Triad-preference and advisory requirements into the canonical project repository schema, including silent exemptions and review-neutral behavior.

Enhancements:

• Archive the ratified prefer-triad-project-shape OpenSpec change after completing its realization evidence and preserve its provenance and records.
• Move the change’s packet from Active to Archived documentation and update the sequencing ledger to reflect the archive.

Documentation:

• Update the README archive index with the completed change and its realization record.

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 19 hours and 53 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

This PR archives the ratified prefer-triad-project-shape change after verifying all realization surfaces—including openRepoProject task 5.6—landed with the required evidence, while promoting the change’s three new advisory and review-neutrality requirements plus the modified elective-schema posture into the canonical project-repo-schema specification.

Sequence diagram for Triad-first project creation

sequenceDiagram
    actor Person
    participant Project as project new
    participant OpenRepoShape as openRepoShape

    Person->>Project: new()
    Project-->>Person: Offer Triad first or single repository
    alt Triad selected
        Person->>Project: Confirm Triad
        Project->>OpenRepoShape: Create Triad without --yes
        OpenRepoShape-->>Person: Request confirmation
        Person->>OpenRepoShape: Confirm creation
    else Single repository selected
        Person->>Project: Confirm single repository
        Project-->>Person: Create single repository
    end

Loading

File-Level Changes

Change	Details	Files
Archives the ratified prefer-triad-project-shape packet and preserves its provenance while recording the realization evidence that satisfied the archive gate.	Moves the proposal packet and related records from the active change directory to the dated archive directory as renames. Updates README active/archive indexes with the archive decision, governance provenance, realization references, and validation results. Closes owner, validation, realization, and archive task boxes with evidence for the governing words, green checks, and merged implementation surfaces.	README.md openspec/changes/prefer-triad-project-shape/tasks.md openspec/changes/archive/2026-10-09-prefer-triad-project-shape/proposal.md openspec/changes/archive/2026-10-09-prefer-triad-project-shape/design.md openspec/changes/archive/2026-10-09-prefer-triad-project-shape/specs/project-repo-schema.md openspec/changes/archive/2026-10-09-prefer-triad-project-shape/tasks.md openspec/changes/archive/2026-10-09-prefer-triad-project-shape/.openspec.yaml openspec/changes/archive/2026-10-09-prefer-triad-project-shape/review/ratification-2026-10-06.md openspec/changes/archive/2026-10-09-prefer-triad-project-shape/review/estate-inventory-2026-10-06.md
Promotes the ratified Triad preference into the canonical project repository schema without making the preference mandatory or review-affecting.	Adds Triad-first preference and migration guidance while retaining elective project shape and human decision authority. Defines advisory behavior, including once-per-session and bootstrap contexts, non-interactive warnings, confirmation requirements, and no automatic conversion or record creation. Explicitly excludes elected Triads, leg clones, family holders, workspace repositories, and projects with an optional staying-single record from the advisory. Adds requirements ensuring project shape never influences review gates, required checks, validators, merge eligibility, or review output.	openspec/specs/project-repo-schema/spec.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[brettheap]

LANDING — lane codeXfactory-5, session ed23f049-7e99-4601-8a6d-760b6aeb5f26@Eagle, 2026-10-09T01:19:42Z, PR #1281 into opensoft/openxFactory main

Landing on Brett Heap's word "merge the archive PR when green" (2026-10-09T00:35:49Z), under his standing word "archive prefer-triad-project-shape when 5.6 lands" (openRepoProject#8 merged green as d7f6b0ee). Every check is green at head 8f93299, including pytest-suite and merge-master-approval; Sourcery skipped. Main has moved one commit (#1261: README and its own change only), and the PR is mergeable. Merging by merge commit, as #1275 and #1252 were.

Lane: codeXfactory-5

[brettheap]

LANDED — lane codeXfactory-5, session ed23f049-7e99-4601-8a6d-760b6aeb5f26@Eagle, 2026-10-09T01:20:02Z, PR #1281 into opensoft/openxFactory main → 35d1d50

Merged at 2026-10-09T01:19:46Z by merge commit, on Brett Heap's word "merge the archive PR when green". This closes the window. prefer-triad-project-shape is archived.

Lane: codeXfactory-5