JesseMarkowitzandClaude Opus 5
1013c94eb1
The media extension contract asks for a scene snapshot a future image or video provider could be handed: location, who is present, what they hold, what must stay true, and where in the story it sits. Building one was the milestone's obvious first task, and it was the wrong one. That snapshot has existed since M5. `narrative_state["scene"]` holds the summary, the location, the cast and the coordinate it was written at; a validated `set_scene` event writes it, every position snapshots it, and every head move restores it. It survives Undo, Redo, Retry, divergence, Save Point restore and a process restart because it is the authoritative state rather than a copy of it. So there is no scenes table here. A second scene store would have been a second answer to "where is the story now", with its own lineage rules to get wrong — and the lineage rules are the expensive part, which is the argument for reusing the ones that already work rather than against it. The Scene Packet is derived on read, and its identity is computed from the campaign and the position rather than allocated: the same position yields the same id in another process, after a restart, and after the packet is thrown away and rebuilt, with no row to keep in step. That is the part of a future media_assets table that would be expensive to retrofit, so it is fixed now even though the table is not built. One table, then: visual_profiles, the only thing the contract's scene list asks for that nothing already stored. Campaign-scoped and not per-position, because a character does not change appearance when the story forks — a reader who diverged would otherwise lose their cast, and the same descriptors would land in every per-position snapshot, measured at 245 copies of 367 bytes in a 120-turn campaign to say something that never varies. Keyed by the M5 entity key rather than a new identity namespace, and one table for characters, locations and items alike, because a location is an entity with a type and splitting them would reintroduce the genre shape M5 spent a milestone removing. What the packet leaves out is the more interesting half. Not the transcript, and not imported knowledge — none of it, not merely the sources marked hidden. The rule is what the story established at this position, not everything the narrator was told, and drawing it by class is what makes it hold for a secret nobody thought to mark. A hidden Canon source proves it, with a positive control showing the narrator did receive the sentinel the packet does not carry. Once a validated event puts the observer in the room, the observer is in the packet: that is no longer narrator-only knowledge, and a packet that hid it would be hiding the story from itself. The providers are contracts and nothing else. Protocols for image, video, audio, speech and transcription, an empty registry, no adapter, no dependency, no socket, and no media setting to point anywhere — a setting that exists can be pointed at a cloud by mistake. A future provider endpoint must be loopback, stricter than narration's trusted-LAN allowance, because a picture of a scene carries the scene with it. Transcription returns an editable draft with no commit method, so STT structurally cannot bypass the authoritative path. Nothing here can write the story. Not by convention: no module under media/ imports the code that writes state, no media event type exists in the state vocabulary, and every test in the authority suite compares the authoritative document byte for byte either side of a media operation — including one where a provider insists Alice is in a red coat in a corridor, and the campaign goes on disagreeing. One defect, found by the milestone's own tests. M10 first added a migration creating an index that create_all already builds from the column, so an upgraded database ended up with two indexes and a fresh install with one. Comparing the two schemas is what caught it; neither database examined alone would have. The migration is gone rather than renamed, and the right number of migrations for a new table whose indexes are declared on its columns is zero. Backend 1,191 passed / 14 skipped / 0 failed, 89 of them M10's. Frontend 145 passed. Lint, production build and Docker build clean. No frontend file changed: M10 adds no reader-facing surface, and ordinary play — turns, state, memory, knowledge, Undo, Redo, Retry, Save Point restore, restart — runs with no media configuration, no warning, no connection attempt and no media row written. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qyn3oRd4D6pi72nKBG725B
64 lines
2.2 KiB
Python
64 lines
2.2 KiB
Python
"""The adventure endpoints, split across one module per group of routes.
|
|
|
|
Importing this package registers every route, because each endpoint module
|
|
decorates its handlers with the shared `router` from `deps`. The import order
|
|
below is the order FastAPI matches paths in. No two routes here shadow each
|
|
other, so the order is for reading rather than for correctness.
|
|
|
|
Read the modules in this order to follow a turn from end to end:
|
|
|
|
deps the router and the ownership check every endpoint runs
|
|
paging reading a window of actions and numbering its attempts
|
|
nodes moving around the story tree
|
|
turns playing a turn, and the lock that allows only one at a time
|
|
takes retries and the attempts that collect at one coordinate
|
|
branches where a story splits
|
|
checkpoints Save Points: durable names for positions the head can return to
|
|
state the authoritative narrative state, and correcting it by hand
|
|
knowledge the imported knowledge library: import, classify, inspect
|
|
|
|
What this package re-exports, and what it deliberately does not:
|
|
|
|
Pure helpers and handlers are re-exported below, so `adventures.ACTION_PAGE` and
|
|
`adventures.undo_turn` keep working. The names a test replaces are not, and you
|
|
must reach those as `adventures.turns.<name>`. Rebinding a re-exported alias
|
|
changes only the alias, so patching `adventures.generate_turn` would leave every
|
|
caller reading the original. Leaving those names off raises `AttributeError`
|
|
instead, which is the failure you want.
|
|
"""
|
|
from .deps import router
|
|
|
|
# Imported for the side effect of registering routes. The names are unused here.
|
|
from . import ( # noqa: F401
|
|
crud,
|
|
turns,
|
|
takes,
|
|
branches,
|
|
checkpoints,
|
|
state,
|
|
bundle_io,
|
|
refresh,
|
|
insights,
|
|
memories,
|
|
actions,
|
|
knowledge,
|
|
visuals,
|
|
)
|
|
from ... import limits # noqa: F401 `adventures.limits` is patched by tests.
|
|
from .crud import SNIPPET_MAX, _snippet
|
|
from .paging import ACTION_PAGE
|
|
from .takes import redo_turn, retry_action, undo_turn
|
|
from .turns import world_delta_of
|
|
|
|
__all__ = [
|
|
"ACTION_PAGE",
|
|
"SNIPPET_MAX",
|
|
"_snippet",
|
|
"limits",
|
|
"redo_turn",
|
|
"retry_action",
|
|
"router",
|
|
"undo_turn",
|
|
"world_delta_of",
|
|
]
|