Name the app's schema once, and split it in two - #35
Open
RISCfuture wants to merge 1 commit into
Open
Conversation
RISCfuture
force-pushed
the
navdata/one-schema-one-factory
branch
from
September 8, 2026 15:48
4b95ec5 to
c36e7a8
Compare
Five places built a Schema of the same ten models, and one of them — PreviewHelper — left out Navaid, surviving only because Leg.navaid drags it in by inference. A prebuilt nav-data store has to match one schema, not five hopefully-equal ones, so there is now a single definition. The models are named in two sets rather than one. Nav data is replaced wholesale every cycle and will arrive as a store file installed by replacing that file; anything the pilot authored has to sit outside the file being replaced. Both sets still open as one store here — the split is a statement of where each model belongs, not yet a second store. NavDataSchema carries a fingerprint over its entities, attributes and relationships, pinned by a test. A prebuilt store is written by one binary and read by another, so the shape they agree on is part of the published contract; an accidental model edit should fail a test rather than migrate a pilot's store. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01471376Uhug2TYZN8RDFGtq
RISCfuture
force-pushed
the
navdata/one-schema-one-factory
branch
from
September 8, 2026 16:32
c36e7a8 to
dea1587
Compare
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.
Five places built a Schema of the same ten models, and one of them —
PreviewHelper — left out Navaid, surviving only because Leg.navaid drags
it in by inference. A prebuilt nav-data store has to match one schema,
not five hopefully-equal ones, so there is now a single definition.
The models are named in two sets rather than one. Nav data is replaced
wholesale every cycle and will arrive as a store file installed by
replacing that file; anything the pilot authored has to sit outside the
file being replaced. Both sets still open as one store here — the split
is a statement of where each model belongs, not yet a second store.
NavDataSchema carries a fingerprint over its entities, attributes and
relationships, pinned by a test. A prebuilt store is written by one
binary and read by another, so the shape they agree on is part of the
published contract; an accidental model edit should fail a test rather
than migrate a pilot's store.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01471376Uhug2TYZN8RDFGtq
Stack created with GitHub Stacks CLI • Give Feedback 💬
🤖 Generated with Claude Code
https://claude.ai/code/session_01471376Uhug2TYZN8RDFGtq