Repository navigation
docs: fix FEDERATION_V2.md's inverted staleness - #10
Merged
Merged
Conversation
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
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.
What
docs/FEDERATION_V2.mdhad drifted stale in the inverted direction: its header and per-sectionstatuses said "design"/"roadmap" for work that actually shipped months ago, per the settled ADRs in
docs/DECISIONS.md. This PR brings the doc's statuses back in line with reality — no code changes.Changes
assistedtask class:— BUILT (D21, R9). Build phases (a) and (b) marked done; phase (c)— explicit
licensed-software/heavy-computecapability-declaration flags at node registration —confirmed genuinely not built (verified via
grep -rn "licensed-software|heavy-compute" council/,no hits) and left open.
BUILT (D22, R10). Rewritten present-tense to describewhat shipped: 256 KiB chunking, sha256 content-addressing, Merkle-root verification,
pw deliver ... @file,pw fetch(percouncil/artifacts.py).PARTIALLY BUILT— links D53 (class-levelpw joinconsent + per-task
assistedconsent) and D24 (reputation/capability gating viastore._meets/store._meets_reputationincouncil/net/store.py), both settled; the declared-capability-flagsgap (same as §0 phase c) is the one remaining open item.
BUILT (D19, R7), not D18 — rewritten present-tense:pw mcp, the[mcp]extra,
council/mcp_server.py, 3 exposed tools (research,library_search,library_add).docs/DECISIONS.mdover restating shipped detail.Verification
ruff check .— clean.pytest tests/ -q— 507 passed, 1 skipped (docs-only change; this is a sanity check the worktreeis otherwise healthy). Note: an earlier full-suite run under heavy shared-host CPU contention
showed 2 flaky failures in
tests/test_agent_loop.py(timing-sensitive real-coordinator-threadtests); both pass individually in <1s and pass again on a clean full-suite rerun once the shared
box's load settled — confirmed unrelated to this docs-only change.
🤖 Generated with Claude Code