docs(vision): mark F1 shipped, restate next deliverable as F2 RBAC wiring#311
Merged
Merged
Conversation
…ring F1 (MySQL <-> SPO oracle parity) shipped via MedCareV2 PRs #1, #2, #3, medcare-rs PR #71, and lance-graph PR #309. The vision doc still claimed F1 was "the next concrete deliverable". Rewrite section 7 to: state F1 has shipped, describe the LanceProbe -> ParityWitness -> DriftSink flow, name the contract DTO (lance-graph-callcenter::transcode::parallelbetrieb::DriftEvent), list F1's known gaps (no latency claims; in-memory ring buffer), and state F2 RBAC+audit wiring (medcare-rs adopting RlsRewriter) as the next posture. No other sections touched.
AdaWorldAPI
added a commit
that referenced
this pull request
Apr 30, 2026
Sprint C agent (PR #311) flagged five staleness items in the vision doc that were out of its §7-only scope. Closing the debt now: Header DRAFT - pending review (2026-04-28) -> Status: F1 parity shipped 2026-04-30. F1 latency benchmark not yet started. F2 is a posture, not a delivery. §2 anchor as of 2026-04-28 -> as of 2026-04-30 (post-F1 parity ship) §2 latency cell Designed to match; F1 numbers (forward tense) -> Designed to match; benchmark pending §2 caveat F1 publishes the first numbers (forward tense) -> F1 parity has shipped (correctness); the separately-scoped F1 latency benchmark has not been started. Distinguishes the two sub-deliverables explicitly. §3 F1 We stand up a Foundry instance... (forward) -> Shipped 2026-04-30. Cross-link to §7's as-shipped architecture. §3 F2 gated upstream by lance-graph PR-1 / PR-2 -> lance-graph PR #278 + #280 + #284 (RLS) and PR #278 + #302 (audit). Status today: lance-graph in production; medcare-rs adopter not yet open. Posture, not delivery. §3 F3 gated upstream by lance-graph PR-4 -> lance-graph PR #278 + #280 (parser + hardening). Status today: parser stub on lance-graph main; medcare-rs adopter is future round-2 work. §4 benchmark harness lands as part of F1 F1 numbers are published (both forward tense) -> F1 parity (correctness) shipped; F1 latency benchmarking has not been started. The two are separately-scoped F1 sub-deliverables. What this PR does NOT touch: - F4, F5, §5 (risks), §6 (NOT promising), §7 (next deliverable just landed in PR #311 - clean already). - The vision doc's tone rule. Every change cites a concrete PR number or file path; no marketing language introduced. - Performance numbers. None claimed; the §4 'do not quote unbenchmarked numbers' rule is preserved verbatim. Diff: +41 / -26 across 1 file. Markdown renders cleanly. Cross-link: PR #311 (the §7 fix that motivated this cleanup).
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
1 participant
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
.claude/medcare-foundry-vision.md§7 was claiming F1 (MySQL ↔ SPO oracle-parity demo) was "the next concrete deliverable". F1 has actually shipped across MedCareV2, medcare-rs, and lance-graph.What §7 said before
"The next concrete deliverable is the F1 oracle-parity demo on a hand-curated 1,000-record subset of clinic data." Followed by a bullet list describing the demo and a closing paragraph promising to publish numbers.
What §7 says now
"F1 has shipped." Followed by three bullets describing the shipped data flow (LanceProbe → ParityWitness → DriftSink → medcare-rs ingest → ring buffer; contract DTO
DriftEvent), an explicit list of what F1 does not yet give us (no benchmarked latency, in-memory queue, hand-curated corpus), and a closing paragraph naming F2 RBAC + audit wiring on the medcare-rs read path as the next posture (not promise).Concrete cross-references the new §7 cites
LanceProbe,ParityWitness,DriftSinkon the C# side.POST /api/__parity/csharpingest endpoint with bounded ring buffer.lance-graph-callcenter::transcode::parallelbetrieb::DriftEvent,DriftKind,Reconcilertrait.crates/lance-graph-callcenter/src/postgrest.rsandcrates/lance-graph-callcenter/src/lance_membrane.rs(whereRlsRewriterandAuditSinkalready live).Test plan
.claude/medcare-foundry-vision.mdon GitHub and confirm the markdown parses cleanly (headings, fenced inline code, list nesting, the table in §2 unchanged).