Remixing Reality's Work Log

Task: field-notes-setup — closed. Remixing Reality now keeps its own field notes: short entries on what the work taught, separate from the records of what the work was. Two-layer home: a content file in the repo is the canonical record, kept in the exact shape a future database could take over (file-before-table, second instance of the MyStatus pattern), and a public "RR Field Notes" stream — rendered on the project's WordPress site — is its projection: approved notes only, wearing their real dates openly, each linking back to the raw update it reflects on. Also shipped: owner config (blog voice; notes derive from session records, never the reverse; capture = staged proof shots + always-recording during device tests) and a Sunday-morning check that drafts the weekly wrapup and waits — nothing is written or posted without approval. Still open, deliberately: Tom creates the public stream, and the reader personas are his to describe, one real voice sample each. Merges (uaal-example): 78921b3c6 + followup d554f4280. Model: claude-fable-5 Tokens: 30 turns · 20,845 written · 82,956 scaffolding per turn · 732,267 weighted total

Task: field-notes-setup (run in-hub). Give Remixing Reality its own field-notes record: a row-shaped content file in the repo that a future RR site can render, plus the owner config that says how it gets fed — voice, sources, capture habits, weekly wrapup slot. Format imported from MyStatus (file-before-table, second instance of the shape). Audiences/personas stay pending Tom's own words. Scaffolding: 82,956 tokens of rules, tools and skills, re-read every turn.

ios-postbuild-autofix — the engine project now carries a post-build hook that edits the exported Xcode project itself: the data folder lands in the framework target and the bridge header becomes public — the two hand-edits previously needed after every export. One merge in the game-engine repository: dec4b9f5. Verification rides the next real export needing zero hand-edits; the status log records that and will be updated when it lands. Tom (guest speaker): "Hallelujah! This is why we have AI to figure these things out! LOL" Model: claude-fable-5 Tokens: 6 turns · 8,219 written · 82,342 scaffolding per turn · 621,712 re-reading itself · 175,195 weighted total

ios-postbuild-autofix — teach the game engine's iOS export to fix its own Xcode wiring. After every export, two hand-edits are currently needed before the host app builds: moving a data folder's target membership and making a bridge header public. A small post-build script inside the engine project will make every export land already correct. Run in-hub, windowed. Scaffolding: 82,342 tokens of rules, tools and skills, re-read every turn.

Text extent containerFrame mapping — done and verified. Text in a remix now keeps its box: the app measures how big a text prop's box actually is when it saves, writes that measurement into the shared document, and the AR viewer lays the text out inside the same box. The size of the letters comes from the size of the box rather than a hand-tuned number — the rule this project has been claiming for weeks and had never made a piece of code follow. Photographed side by side in both, letter height matched exactly. A remix saved before today has no box recorded in it, so the AR viewer falls back to what it did yesterday for that one — unchanged, and still not a match for the app's own view. It heals the next time that remix is saved, because the app measures every text prop it saves, not only new ones. Verified: 30 tests, 0 failures on the Mac; device pair in both lanes. A first size estimate off a stretched photo pair suggested a 25% gap and was wrong — the two shots were taken from different distances; a controlled pair showed no gap. Two unrelated pre-existing problems surfaced while checking and are written down: the debug sheet's legacy view serving a stale snapshot, and text outlines not yet drawn in the AR viewer. Merges: game-engine repo 59a71465 · AR-viewer repo 3069464 · host repo d458095f9, wording followup 461fa6a48. Model: claude-opus-5 Tokens: 66 turns · 61,062 written · 82,935 scaffolding per turn · 6,202,955 re-reading itself · 1,858,513 weighted total

Text extent containerFrame mapping — device shots are in and the feature works: the text box crosses into the AR viewer, the layout settings it carries are honored, and nothing reported a problem it shouldn't have. One number is off. Using an image prop in both photos as a common ruler, the text in the AR viewer measures about three quarters the size of the same text in the app — close, clearly the right ballpark, but a real gap. Cause looks like two different definitions of "font size" being treated as one. Proposing one more iteration to separate them before merging.

Text extent containerFrame mapping — both halves written and committed: the app now measures a text prop's box when it saves and writes it into the document, and the AR viewer lays text out inside that same box. The glyph-to-box proportion that was frozen inside the app's prefab and written down nowhere has been measured and recorded. Handing off to Tom for the checks that need a Mac and a phone.

UserSettings gitignore exclusion Opening the game engine's editor used to dirty the project. Window layouts, the search index and editor preferences all lived in a folder the project's history was watching, so simply launching and closing the editor produced changes that had to be waved away by hand every time. That folder is now ignored and no longer tracked. The files stay on disk exactly as they were — the history just stops watching them. Verified by opening the editor and finding the working copy still clean. The build-configuration file that churns the same way is deliberately untouched. That one is real settings, and it stays tracked. Merges: game-engine repo 3f8e2c9d · host-app repo 3233341dd (status-log entry only) Model: claude-opus-5 Tokens: 17 turns · 8,081 written · 82,118 scaffolding per turn · 596,600 re-reading itself · 461,212 weighted total

UserSettings gitignore exclusion Unity writes per-user editor state — window layouts, the search index, editor preferences — into a folder that has been tracked in the project's history all along. The result is that simply opening or closing the editor shows up as repository churn that has nothing to do with anyone's work, and it has to be waved away by hand every time. This task adds one ignore line and stops tracking that folder. The files stay on disk, untouched; only the project's history stops watching them. Deliberately not in scope: the build-configuration file that also churns. That one is real settings, and it stays tracked. Scaffolding: 82,118 tokens of rules, tools and skills, re-read every turn.

RemixTextAPI layout attrs converter Merged: 76f4cbf97 (uaal-example) A piece of text in a remix has always carried what it says, its font and its colours. It has never been able to say how it sits: how big its box is, how the words align inside it, whether they wrap, which backup fonts to use if the first one is missing, or whether the text turns to face whoever is looking. Those eight properties were added to the shared description format in early August, but nothing could carry them between the app and the document — a vocabulary with no speakers. This teaches the whole path to speak them. The names were settled first, before any code: plain names sitting directly on the text, matching the shared format one for one. Two decisions worth knowing about, both following rules the project already had. If a value isn't one the format recognises, it is kept exactly as written rather than written down wrongly. And an empty list of backup fonts is kept as an empty list rather than recorded as a decision to have none. Proof is the round trip: all 975 test documents were turned into documents and back into their original form, and every one came out byte-for-byte identical, with no exceptions granted to anything. The checker passed 1,952 of 1,952 files clean and the two independent writers agreed. Worth recording: nothing was compiled while it was being written — this machine has no Swift toolchain — so the expected document output was worked out by hand, the same bet as the schema file earlier this month. It matched byte-for-byte on the first run, as did three pieces of library plumbing that had never been used from this side before. Nothing looks different yet. The app doesn't produce these values until the next piece of work; this is the road being built before the traffic. Model: claude-opus-5 Tokens: 66 turns · 60,413 written · 82,381 scaffolding per turn · 9,629,148 re-reading itself · 2,559,186 weighted total

RemixTextAPI layout attrs converter Implementation committed — the eight layout properties now travel the whole path: read off the JSON, written into the document, read back out again. New test fixture covers the three interesting cases in one file: a fully described piece of text, one with values the schema doesn't recognize (kept verbatim rather than written badly), and layout properties attached to something that isn't text at all. One thing worth flagging: this sandbox has no Swift toolchain, so nothing here has been compiled. The expected document output was worked out by hand instead — same approach as the schema file in August, which turned out byte-identical to the generated one. Tom's Mac run is the real check. Next: hand-off notes and the verification ask.

RemixTextAPI layout attrs converter Teaching the JSON⇄USD converter the eight text-layout properties that shipped in the schema on 8/10 — how a piece of text is boxed, aligned, wrapped, and whether it turns to face you. The schema already describes them; nothing has been able to carry them over the wire. This task gives them names in the JSON dialect, teaches the converter to write them into the document and read them back out, and proves a document survives the round trip unchanged. No visible behavior changes yet — the app doesn't author these fields until the next task. Design decision settled with Tom before any code: flat, bare key names on the text prop (extent, anchor, halign, valign, wrap, fit, fontFallbacks, facing), with extent shaped {x, y} like every other measured field. Names map one-to-one onto the schema properties. Checked first: across 1,540 text-and-prop nodes in the corpus, none of the eight names is already taken. Scaffolding: 82,381 tokens of rules, tools and skills, re-read every turn.

multi-repo-constellation — the project's three repositories now work as one. The host-app repo is the anchor: it holds every process document — status log, task prompts, session capture, receipt scripts, and the law itself. The other two are satellites carrying a short pointer back to it. From now on a single task keeps one public record and one branch name across every repository it lands code in, and it can't close while any repository still holds an unmerged branch. The pattern also went into the shared git-workflow skill so other multi-repo projects inherit it. Found along the way: the file-delete permission is per-repo — this task itself left stale git locks in both satellites before learning it; the lesson is now in the skill. Merges: uaal-example 7904629ca · UnityProject 72a4ba4c · USDtoReality 178cc5d Model: claude-fable-5 Tokens: 12 turns · 17,891 written · 80,709 scaffolding per turn · 912,949 re-reading itself · 600,655 weighted total

multi-repo-constellation — the project is three repos that should have been one (host app, Unity project, converter library), and until tonight only the host app knew about the working process. This task writes the constellation law: the host-app repo becomes the anchor holding every process document, the other two become satellites carrying a pointer, and one task now means one record and one branch name across every repo it touches. Docs only, no product code. First task run under its own rule — it touches all three repos. Scaffolding: 80,709 tokens of rules, tools and skills, re-read every turn.

Process kit bootstrap — the Remixing Reality repo now runs the working process end to end. What landed: the process law written into the app's CLAUDE.md (branch model, lifecycle posting, receipts, capture, status conventions) with sockets for RR-specific rules to grow into; a status log, a vetted-prompts file, and a live session-capture folder under docs/; the three receipt scripts copied from the hub and verified running against this repo; and a preflight script that honestly records there are no headless build gates yet. Zero product code. Found along the way, fed back to the hub: the dispatch undercounted the script kit (three files, not two — session-tokens.mjs imports transcript-models.mjs), and the session's own git status stale-locked the repo, briefly blocking Tom's commit — the exact failure the seeded law documents. Merge: 2f7a018e5ed87fddf3728724f3d8d34577f2d480 Model: claude-fable-5 Tokens: 28 turns · 27,281 written · 81,340 scaffolding per turn · 1,671,993 re-reading itself · 806,908 weighted total

Process kit bootstrap — all three receipt scripts are in and verified against this repo (the dispatch said two; session-tokens.mjs imports a third, transcript-models.mjs — hub prompt to be corrected). The figure the Open owed: Scaffolding: 81,340 tokens of rules, tools and skills, re-read every turn. Close draft is next; awaiting Tom's approval.

Process kit bootstrap — seed files built and committed (CLAUDE.md law section, docs scaffolding, preflight, live session capture, both channel configs). Now waiting on Tom to copy session-tokens.mjs and daily-log.sh over from the hub repo — the receipts can't be measured until the measuring stick is in the drawer.

Process kit bootstrap — installing the working process into the Remixing Reality repo: branch model, lifecycle posting to this task, docs scaffolding, receipt scripts. Zero product code. Branch process-kit-bootstrap cut off the new claude integration branch (claude itself created off main this session — first task in this repo under the workflow). Scaffolding figure: not yet measurable — session-tokens.mjs lands as part of this very task; the figure follows in a beat once the script is in place.