Files
Dune/docs/EFFICIENCY_PILOT.md
T
Quintine f0256c1b38 Prototype Discovery spice encounters, private tokens and stash rewards
Connect real Basic/Advanced base-faction audit setup to all seven Discovery
Spice Cards and eight physical tokens. Add Great Maker's ordered majority
vote and Fremen reserve ride, destructive Discovery blows, private faction
peeks and Collection inspection/reveal, stash rewards and mandatory saved
card overflow, and revealed nested board locations. Share private legal
choices with human controls and all four AI profiles. Preserve normal gates.

Independent review repairs orphaned worm/vote/ride controls, retargeted
reserve arrivals, actor bindings and incomplete overflow discard receipts.
Harden room-aware admission against unrevealed nested locations. Extend the
backed-up local prototype starter with a Discovery profile; preserve seats.

Still missing: next-turn free entry, five special location benefits and
Ornithopter movement spending. Current prototype playthroughs do not certify
those effects or complete module/expansion compliance.

Verification: npm run check passed 4264 offline tests plus types/lint;
npm run build passed; npm run test:integration passed 40 tests. The single
source-bound broad run took 129358ms / 6782ms / 23918ms respectively.
Report: /home/quintine/.local/share/dune/checkpoints/20260913-discovery-prototype/verification/report.json
Source fingerprint: 4ea7b5209a58c369b0b1f8dc239b5dd2f3302bb759d83c32ba5406e80d8ae154

Two seeded Basic/Advanced games complete with component custody intact.
SQLite races pay stashes once and resume committed discards without replay.
Browser 3RJBH26Y verifies genuine human Fremen setup, a Discovery blow from
one reordered physical card, native private Hiereg visibility, enlarged
card/rules reading and refresh. Room remains paused at spice acceptance.
All 125 opening saved rooms unchanged; 31 added, 156 total. No server restart.

Efficiency: three reused bounded helpers; aggregate counter 60591430 to
61812513 after verification, 1221083 tokens before final Git/push overhead.
47 added offline tests. One stable broad run after focused review fixes;
no calibration or exhaustive optional-module interaction matrix.
2026-09-13 13:27:58 +10:00

107 lines
8.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Three-milestone efficiency pilot
Preserve the complete game scope and required checks. Use small relevant reads,
coherent feature batches, selective subagents and compact verification artifacts.
Git remains mandatory: review, verify, commit, push and confirm remote success at
each finished implementation checkpoint. Never force-push or commit credentials.
The removed recurring automation stays removed.
| Milestone | Deliverable | Measurement |
| --- | --- | --- |
| 1: setup | Current status, decision index, reusable checks, saved-game snapshots/backups and HTTP seat restoration | Accepted checkpoint `6e26ba5`. Aggregate counters 57,957,554 → 58,124,416: 166,862 tokens including planning, coordination and the user-requested save reset. Two bounded helpers. Fifteen added regressions; 4,177 offline tests passed. Three broad attempts: two stopped before tests on type/lint errors; final check passed in 130.147s. One cancellation defect found and fixed in review. |
| 2: core readiness batch | Typed Advanced reserve-shipment commitments without Guild or optional modules | Accepted checkpoint `32791ed`. Aggregate counters 58,124,416 → 58,695,053: 570,637 tokens. Two bounded helpers: regression implementation and independent rules/privacy review. Fifteen added tests; 4,192 offline and 40 HTTP tests plus build passed. One stable broad run; focused checks resolved setup mistakes and two review findings before it. Two browser rooms verified distinct AI and human paths. Pending Guild settlement remains explicit. |
| 3: next dependency batch | Truthtrance total hand size and primary-role counts, controls, bots and recovery | Accepted checkpoint `7454456`. Aggregate counter 58,695,053 → 59,144,653 at completed verification: 449,600 tokens, before final Git/push overhead. Two workhorse-model helpers for regression implementation and independent review. Reused count panel and SQLite fixtures; eight added tests and expanded recovery cases. Two copy issues fixed before the single stable broad run: 4,200 offline tests, build and 40 HTTP tests passed. One browser room covered combined roles, total size, invalid input and phone refresh. |
The aggregate counter may update only between turns. Record a confirmed endpoint
when available rather than estimating missing usage. It includes coordination and
conversation overhead and is not a dollar-cost meter. Different capability sizes
limit direct comparisons; do not promise a savings percentage from this setup.
Do not count tests alone as accepted faction or mode completion. Scripts consolidate
existing checks; broad checks still run once source/review is stable and repeat if
subsequent changes or failures justify them. Browser fixtures remain feature-specific;
the reusable HTTP restoration helper does not automate browser setup or visual QA.
Milestone 2 cost more than the tooling baseline and cannot establish a saving.
Its larger rules/interaction scope, browser setup and context recovery contribute
to that total. Milestone 3 was smaller and reused more existing structure; its lower
count cannot isolate the effect of model choice or establish a savings rate.
Avoid repeatedly loading old audits. Three different deliverables alone cannot
support a reliable percentage estimate.
For initial planning, allow roughly **450,000–575,000 aggregate tokens for a
similarly sized reviewed gameplay batch**, based on milestones 2 and 3. This is a
low-confidence planning estimate, not a dollar quote, token-budget setting or a
reason to stop required work. Larger interaction sets need a revised estimate.
The tooling baseline was about 167,000 and is not a gameplay cost target. Reassess
after the next few comparable batches, including defects found after acceptance.
Next adjustment: use the owner plus one bounded helper for source research and
independent review when the existing implementation needs verification. Reuse
the same helper for its follow-up review, existing fixtures and applicable checks.
Avoid adding runtime code merely to make an audit appear to be implementation.
The full-plan interaction audit starts at aggregate counter 59,151,671, uses that
one-helper pattern and changes tests/documentation. It therefore requires the
full offline check, but can reuse the unchanged application's earlier build;
browser/restart acceptance supplies direct recovery evidence. Checkpoint `4a0b1ee`
passed all 4,205 offline tests in one stable broad check. Its aggregate endpoint
was 59,509,237 at completed verification: 357,566 tokens before final Git and new
goal-steering overhead. It is an audit batch, not a new gameplay capability.
## User-directed rapid prototyping, 13 September 2026
The first batch starts at aggregate counter 59,524,858 and connects genuine Ix
setup to the existing faction/card gameplay and saved browser table. One bounded
helper inventoried existing work and implemented focused tests; a second reviewed
setup privacy and the local database writer. The owner integrates the prototype
entry, reusable backed-up starter, checklist and browser journey. Six added tests
include two fixed-seed complete games without a calibration study. A saved-version
review finding and a test typing error were fixed before the stable broad check;
final results and counter endpoint are recorded in the checkpoint commit.
Prioritize functional coverage of the entire remaining game before exhaustive
per-feature refinement. Use the existing checklist to distinguish missing,
prototyped, integrated, verified and polished functions, and choose connected
batches by dependency across core and expansion systems. A prototype includes
a working action, usable controls, legal AI participation and saved continuation.
Track functions newly playable and issues discovered during integration, alongside
tokens and rework; do not count placeholders as delivered functions.
Keep focused invariant and smoke checks during prototyping and required checks
at stable checkpoints. Use integrated games to find defects; defer exhaustive
combination testing, AI calibration and final visual polish to refinement unless
an active defect requires them sooner. Preserve material rule questions, mode
gates, selective subagents and automatic verified Git pushes. The earlier batch
estimates remain historical planning evidence and should be reassessed for this
broader prototyping workflow, without an assumed savings percentage.
Check account usage after each verified checkpoint. The user explicitly confirmed
the stop point as **80% weekly usage consumed (20% remaining)**. Keep the goal
unfinished when stopping for usage, preserve Git and subagent requirements, and
leave the removed recurring automation absent. After `32791ed`, usage was 3% used.
Use [current status](CURRENT_STATUS.md), [rule decisions](RULE_DECISIONS.md) and
[verification workflow](VERIFICATION_WORKFLOW.md) as short entry points. Historical
logs remain references, not mandatory full-context input on every turn.
The next rapid prototype batch begins at aggregate counter 59,982,405 and adds
one missing action: CHOAM Nexus Secret Ally Collection trade. A workhorse helper
acquires the complete Discovery inventory for the following batch; a reused
independent reviewer checks this trade and its queued-Collection lock. The owner
connects runtime, private controls, AI and SQLite recovery. The battle inspection
alternative stays explicitly missing instead of holding the independent trade
for an exhaustive battle-cleanup design. Final checks, counter endpoint and
checkpoint scope are recorded in the commit.
The Discovery batch starts at aggregate counter 60,591,430. Three bounded helpers
cover physical inventory, nested board/admission, and private controls/docs;
reusing them adds deterministic playthroughs and independent review of the
owner's encounter/reward integration. New playable functions are Great Maker's
vote/reserve ride, six Discovery blows, private Collection inspection/reveal,
and both immediate stash rewards with saved overflow discard. Token custody
and board destinations prepare the following location/flight batch. Reused
room-start tooling now selects the Discovery profile. Reviews found and repaired
lost saved controls, a retargetable arrival and skipped overflow discard before
the stable broad check. The implementation adds no calibration study or server
restart. Final aggregate endpoint, source-bound checks and push belong in the
checkpoint commit; whole-module completion remains unclaimed.