May 12, 2026
Gideon Build Log: Approval Became The Save Trail
May 12 was not about adding another room to Gideon.
It was about removing uncertainty from the room that already mattered.
The working question was simple:
When a scene moves from discussion to edit to approval, what becomes live?
That question matters because Gideon is not just helping generate text. Gideon is becoming a story production workspace. A workspace has to know which scene is current, which output is scratch, which version was approved, and which file became source memory.
The Scene Card Became The Living Record
The old flow still had too many save-like moments:
Build Card.
Approve Scene.
Save Card to Repo.
That made the writer ask the wrong questions.
Which version is live?
Which version is stored in the workspace?
Which version is in the repo?
Did Gideon save the visible card, or an older stored card?
That ambiguity is dangerous in a story system.
The better model is:
Scene Card equals living record.
Every time the scene passes through a working tier, the same card should gain a stamp.
Chart the Waters.
T1.
T2.
Later, Forge validation if the captain chooses.
The scene card should remember the path, not just the latest output.
The card now needs to answer four questions quickly:
What is this scene?
What is the current approved state?
Which pass got it here?
Where is the repo-backed source?
That is the difference between a generated artifact and production memory.
A generated artifact can be useful once.
A living scene card keeps the workspace honest.
Discuss And Edit Became Separate Commitments
The important product distinction became:
Discuss is scratch.
Edit prepares the live change.
Approve Scene makes it accountable.
That maps to the way the writing actually happens.
Sometimes the writer wants to talk to Gideon about options, pressure points, alternate paths, or whether a choice works. That should not change the scene.
Sometimes the writer wants Gideon to apply selected notes to the current page. That is Edit.
Those are different commitments.
The bridge became:
Use In Edit.
After a Discuss output, the writer can now send that thinking into Edit without manually copying it.
The edit prompt is preloaded with:
Approved Discuss Notes.
Captain Notes.
Edit Request.
That makes the flow feel like one working conversation instead of three disconnected operations.
Approval Became The Serious Save
Approve Scene now does the serious work.
It saves the edited output as the current live scene.
It adds the tier stamp.
It refreshes the living Field Scene Card.
It writes the card to the repo.
It records the approval in the decision trail.
That is the save trail Gideon needed.
This matters because the writer should not need to remember a secret button order.
The old mental model was:
Build Card.
Approve Scene.
Save Card to Repo.
The new mental model is cleaner:
Discuss is scratch.
Edit is the candidate live change.
Approve Scene saves, stamps, and backs it up.
EP203 Started Moving Faster
The product changes were not theoretical.
They were tested inside the EP203 working lane.
A1S3 moved from Chart the Waters to T1.
A1S4 moved from Scene Pack to Card, then from edited Chart work to scene beats at T1.
A1S5 moved through Add Scene, Chart the Waters, Build Card, Approve Scene, and repo save.
A1S6 went in faster than the earlier scenes.
That speed matters.
The work got faster because the workspace got quieter.
Less guessing.
Less save anxiety.
Less wondering whether Gideon was changing the page or only talking about it.
The writer could stay closer to the scene.
That is the point of the product.
The Current Product Shape
By the end of the session, Gideon had a cleaner working contract:
Episodes holds the project tree.
Add Scene creates a clean intake lane.
Writing Session holds Discuss and Edit.
Discuss is scratch thinking.
Use In Edit carries chosen thinking into application.
Edit prepares the live candidate.
Approve Scene saves the live version, stamps the tier, refreshes the card, and writes to source.
Forge remains later validation and quality control.
Scene Card is living source memory.
Log Book preserves the decision trail.
The important product truth is becoming stable:
A note is not the scene.
A discussion is not the scene.
A validation report is not the scene.
A scene becomes live only when the writer approves it.
That boundary protects authorship.
What Still Needs Testing
The next pass should test the new approval loop deliberately.
Open a current EP203 scene.
Run Discuss at the active tier.
Confirm Use In Edit appears.
Send the output into Edit.
Add one Captain Note.
Run the Edit pass.
Confirm Approve Scene unlocks.
Approve Scene.
Confirm the card receives Tier Stamps and Live Workspace Save.
Confirm the repo file updates.
The watch points are clear:
No Discuss output should become live by accident.
No scratch note should save as scene text.
No stale card should write to repo.
No stale active scene should leak into a new scene.
The scene card should remain the source memory, not another loose output.
Product Truth
May 12 made the save trail clearer.
Gideon is less useful when it gives the writer more outputs to manage.
It is more useful when it protects the difference between thinking, editing, approving, and saving.
That is where the product is heading.
The scene stays the anchor.
The writer makes the call.
Approval becomes the record.
