docs: state the support boundaries, ADR outcomes and baseline lifecycle - #416
Merged
Merged
Conversation
The reference described these three in prose that a reader had to reconstruct. Give each the shape it is actually read in: a per-artifact table of build target and supported host, a table of the four ADR-check outcomes and the action each requires, and the four steps a GenDoc baseline goes through. Salvaged from agent/extract-adr-specifications, whose separate specification pages this reference had already superseded. Every claim was re-verified against the current tree: target frameworks, roll-forward policies, RoslynFloorVersion, and the fce catalog subcommands.
Reefact
force-pushed
the
claude/adr-implementation-reference-detail
branch
from
August 10, 2026 19:33
dd44852 to
0fd3097
Compare
Reefact
enabled auto-merge (rebase)
August 10, 2026 19:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Gives three contracts the ADR implementation reference already described in prose the shape they are actually read in — two tables and a numbered lifecycle. Salvaged from the abandoned
agent/extract-adr-specificationsbranch, whose separate specification pages this reference had already superseded.Type of change
Changes
net8.0split is readable at a glance instead of reconstructed from two paragraphs.fce catalog update.The analyzer row points at
RoslynFloorVersionrather than restating the version: the reference already declares that property the single source of truth, and a copied number drifts.Testing
Documentation-only change; no code is touched, so the build and test commands were not run for this branch. What was verified instead — every factual claim added here was re-checked against the current tree:
TargetFrameworkvalues;Majoron the CLI,LatestMajoron the worker, none on GenDoc);RoslynFloorVersion,RoslynFloorTestsandbuild/Net472TestFloor.props;fce catalog updateandfce catalog diffregistrations inCliApplication.Structural checks: English and French are symmetric (121 lines, 9 sections, 2 tables, 1 numbered list each), the four new tables are well-formed, and all 30 relative links resolve.
Documentation
doc/updatedArchitecture decisions
This is implementation mechanics, which is what the reference exists to hold; no decision is recorded, changed or contradicted.
Related issues
None.
🤖 Generated with Claude Code
https://claude.ai/code/session_01JLxWJd3puHgDCdQoSiCgZC
Generated by Claude Code