Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Prioritized execution register

Updated: 2026-10-12

This register accounts for every open issue at the start of this implementation campaign. Priority follows security and correctness dependencies, not issue age. P0 restores a trustworthy development baseline; P1 delivers the operational loop; P2 measures and extends it; P3 carries explicit demand/architecture gates. A gated issue is not an implementation authorization to bypass its acceptance criteria. Priority is not a completion claim.

Current sequence

  1. SYN-330, hook/test fixes and numbering hygiene.
  2. SOMA-34 Rust account/authority foundation, then measured usage and adapter guarantees.
  3. Synapse transition integrity/identity and Soma capability/context/event contracts.
  4. Versioned knowledge integration, deterministic diagnostics and two-operator pilot.
  5. Retrieval/semantic/source/visual extensions and demand-gated infrastructure.
PriorityIssueNext evidence or dependency
P0SYN-330: resolve advisory and yanked dependency CI blockersCompatible security fixes; maintained YAML; all gates
P0SYN-328: isolate Git hook environment from temporary-repository testsImplemented in PR #315; awaiting security gate
P0SYN-329: keep audit test fixtures within the retention windowImplemented in PR #315; awaiting security gate
P0SYN-322: define the composable knowledge framework and trust architectureArchitecture in PR #315
P0SYN-236: renumber stale backlog issues off the colliding SYN-200..210 schemeResolve task ID collisions without changing historical commits
P1SYN-261: cryptographic SSHSIG commit verification (multi-user)Actual SSHSIG validity before treating presence as assurance
P1SYN-324: seal governed state transitions and detect unjournaled Markdown driftDurable governed transitions and source drift
P1SYN-325: persist signed receipts and add fail-closed verification profilesPersist receipts and explicit fail-closed policy; depends #309
P1SYN-318: Memory CI with explicit verification policy and coverageMemory CI coverage; depends #310
P1SYN-326: bind OIDC subjects to offline signing keys and scoped approval authorityIdentity binding and scoped authority; consume Soma account contract
P1SYN-231: shared knowledge authority and governed team acceptanceTeam authority, after transitions/identity
P1SYN-319: scoped contradiction diagnostics (CLI + MCP)Expose existing deterministic contradiction diagnostics; ML remains separate
P1SYN-321: embed Synapse in Soma through a versioned knowledge contractVersioned CLI knowledge contract; coordinated with SOMA-39
P2SYN-323: evaluate local NLI and Jev-style typed knowledge decisionsLocal NLI/typed decision benchmark with abstention and EN/PT fixtures
P2SYN-335: optional source adapters for documentation revision monitoringSource revision adapters, begin with Git and API schemas
P2SYN-327: track source revisions and scoped shared API knowledge impactShared API impact; depends #96 and #308
P2SYN-320: standard verification attestation envelopes (in-toto; C2PA optional)Attestation envelopes after persisted receipt contract
P2SYN-109: documentation site on GitHub PagesPublish docs with explicit delivered/proposed scope
P2SYN-302: syn graph serve - real-time interactive graph in the browserLocal graph UI; includes legacy #234 requirements
P2SYN-246: localhost graph UI server (Stage 2)Legacy stage covered by #290; consolidate without dropping security criteria
P2SYN-295: re-validate the flat-vector ceiling before HNSW (SYN-225)Measure actual flat vector limits before HNSW
P2SYN-307: on-device retrieval-model options - E5 asymmetric seam, EmbeddingGemma, MRL (ADR-045)Retrieval model seam/evidence; do not silently install gated models
P2SYN-313: spike - wire the discarded BGE-M3 sparse output as a retrieval legSparse output experiment; ship only on measured retrieval benefit
P2SYN-336: simultaneous multi-workspace from a single MCP serverMultiple workspace routing; authorization and mutation boundaries first
P2SYN-337: remote federation - syn remote add <git-url>Remote Git federation with explicit trust/fetch boundaries
P3SYN-331: encryption at rest for .synapse/index.dbIndex encryption is separate from source confidentiality; define threat model
P3SYN-334: support TOML frontmatter as alternative to YAMLTOML alternative after stable shared knowledge contract
P3SYN-235: MCP over HTTP/SSE - hosted gateway building blockHTTP MCP transport when a consumer justifies it; do not duplicate Soma authority
P3SYN-317: resident always-on MCP server (OS auto-start + catalog discovery)Resident daemon only after measured process-overhead trigger
P3SYN-174: restore Intel macOS (x86_64-apple-darwin) - ort-tract or ONNX from-sourceIntel substrate proof without adding an untested second runtime
P3SYN-233: verifiable identity / CV layer (signed, checkable attestations)Identity/CV evidence outside the initial operational product slice
P3SYN-232: declare explicit open-core boundary (governance/compliance edition)Commercial/open-core boundary requires product evidence and license decision
P3SYN-230: ‘syn sync’ - optional end-to-end-encrypted vault sync (hosted + self-hostable)Hosted encrypted sync after authority and durable protocol
P3SYN-286: (gate) HNSW vector index when the corpus crosses the budgetHNSW explicitly gated by #283 measurement and real demand
P3SYN-225: swap sqlite-vec flat scan for HNSW (vectorlite) - execute ADR-008 pre-staged planOlder HNSW issue superseded by explicit gate #274
P3SYN-333: desktop GUI (tauri)Desktop GUI demand evaluated after Soma integration
P3SYN-332: TUI (ratatui) interactive modeTUI demand evaluated after CLI/API workflow

Completion rules

Use small reviewable changes, linked ADRs and focused regression evidence. Every PR records actual checks and remaining acceptance criteria. Close delivered issues through the finishing PR; consolidate duplicates with links and preserve their unique requirements. Do not describe a stub, design document, unavailable live credential or skipped measurement as implemented. Account service credentials belong only on the backend. Do not rewrite existing user changes or old commits.