Decision and snapshots
Human authority, immutable corpus state, provenance, and atomic local generations.
Strict Core invariants · Flexible workflow profiles
A dependency-ordered route from local authority to connected operation
Each feature requires its own accepted decision, negative cases, fixtures, validation, and explicit non-claims. Later convenience never weakens earlier authority.
Completed foundation and conduct
Deduplication conduct
Previewed and confirmed human decisions with corrections and successor snapshots.
Execution journal
Replayable protocol-bound work state and append-only transitions.
Screening
Independent human review, conflicts, adjudication, and invalidation.
Local full text
Exact bytes, derived extraction evidence, and full-text decisions without retrieval.
Reporting and bundles
Conserved counts, Rapid Review governance, exports, and verification.
Evidence analysis
Extraction, appraisal, and plan-only synthesis with evidence and correction lineage.
Local desktop
Product host, safe commands, deduplication decisions, and Screening authority readiness.
Next candidate inside FE-08
Slice 5 — first desktop title/abstract Screening conduct
The protected-main roadmap identifies Slice 5 as the next candidate after durable authority resolution. It must preserve exact actor, criteria, snapshot, protocol, workflow, and expected-state bindings. A separate accepted ADR and gate are required before implementation.
Sequenced future capability
Providers and networks
Legally governed external acquisition and reproducible citation-graph evidence.
Plugin runtime
Capability-scoped, out-of-process execution with staged and validated output. Current code contains only a small contract scaffold, not a host or sandbox.
Governed AI
Evidence-bound model proposals with explicit privacy and human acceptance.
Connected operation
Database, API, cloud, synchronization, authorization, and multi-user infrastructure.
Why connected infrastructure comes last
Persistence and distribution amplify semantic mistakes. Stable local records, invalidation, command behavior, and operator workflows come first.
FE-10 in concrete developer terms
FE-10 is planned as an outward runtime boundary for untrusted extension code. A plugin would declare identity, versions, input and output schemas, requested capabilities, data classification, resource needs, and network or credential requirements. The host—not the plugin—would resolve an explicit grant for one project or invocation.
Manifest
declare identity and needs
→
declare identity and needs
Grant
select scoped capabilities
→
select scoped capabilities
Host
run out of process
→
run out of process
Stage
write non-canonical output
→
write non-canonical output
Validate
schema, digest, policy
→
schema, digest, policy
Adopt
separate domain or human action
separate domain or human action
Critical boundary: a separate process improves isolation but is not, by itself, a security sandbox. A plugin receives no database credentials, unrestricted workspace path, raw secret, or authority to make its staged output canonical.
Read the current Extensibility scaffold and full FE-10 non-claims.
How a roadmap item becomes real
- Resolve source conflicts through an accepted ADR.
- Define authority, identity, provenance, invalidation, privacy, and trust boundaries.
- Specify positive fixtures and adversarial negative cases.
- Implement one coherent vertical slice without widening adjacent modules.
- Pass focused tests, architecture checks, full Release validation, package smoke, and formatting.
- Record completion evidence bound to the tested commit and preserve explicit non-claims.