Contribution Map: four-review pilot#
For the author's review. Mission run_request:a89d1522-b36e-4434-8ac8-0d75495803b2, accountable circle Evaluation, Continuity contributing. Rendered from contribution-map.json.
Every row is a suggestion with its decision pending. The order is by value type and then by id, and it is not a ranking. A suggested action authorizes no work. Only the author validates priority.
CM means Contribution Map candidate. Reviews:
| label | review | version | video |
|---|---|---|---|
| PI | miadi-review://2df86bf3-1bfc-44e9-a505-b4321a146498 | v3 | https://youtu.be/uqqTMx47SbY |
| PII | miadi-review://479a8e61-1882-41ba-b097-9fc25329efa5 | v2 | https://youtu.be/0iKyoMU5jDs |
| NL | miadi-review://8031484c-fab8-4061-8cb1-094306ad4002 | v4 | https://youtu.be/38rsaFfX10g |
| RR | miadi-review://2c8c8f1d-43da-49cf-b4ee-a9cf118658e0 | v17 | https://youtu.be/SEHA22a-VlE |
Status words: observed, author_reported, inferred, proposed, verified_independently, unknown. A timestamp is copied from the review and is generated and unverified. Asks the author now is yes only when all four Knowledge Focus Ethics criteria hold, by this session's answers in the JSON. RC codes point at receipts in evaluation-and-gaps.md.
Creative#
| id and question | source and status | existing issue | beneficiary | tension | possible contribution | smallest proof | circle | suggested action | asks the author now | decision |
|---|---|---|---|---|---|---|---|---|---|---|
| CM-01 Is a voice injected during the shoot a production method to develop, with injected turns kept apart from the person's turns in the transcript? | RR v17, "keypoints by apple", author_reported, author's note: "Itβs a way to inject audio content within the actual shooting that Iβm doing." RR v17, "keypoints by apple", author_reported, author's note: "this layer where Iβm capable of generating different voices including my own to actually interact to influence the actual discussion" RR v17, "Results" at 1:14:00-1:16:00 (generated, unverified), inferred, generated review text: "critical arguments regarding agent bounding and shared intention are rendered into spoken audio and archived in Scrivener" NL v4, "3.3. Dialectical persona scaffolding β candidate 40:05β42:30" at 40:05-42:30 (generated, unverified), proposed, assistant-written version: "not a transcript of five autonomous agents independently deliberating" NL v4, "stored transcript turn 49:02" at 49:02 (generated, unverified), author_reported, Gemini stored transcript: "I love this podcasting house line proposal." | jgwill/Miadi#920 (open) jgwill/miadi-orchestration-kit#107 (open) | The author while shooting, then whoever watches and reads the recording. | Now: the author's method is described as a delay, and the author says the voices often lack context. To exist: a shoot segment where an injected voice carries chosen context and the transcript can tell it from them. | One segment the author picks, recorded the author's way, with its transcript marked by hand. No build. | Reliability: One transcript of a chosen segment where every injected turn is labelled and differs from the person's turns, checked by listening to that segment. Agency: The author says whether the injected voice changed what they did next in the shoot, in their own words, kept beside the segment. | Story with Evaluation, Stewardship | Creative experiment | yes | pending |
| CM-02 Do the four candidate beats and the interruptions they draw on stay available for a film or Twine passage? | NL v4, "8. Candidate narrative beats β Offered to the author, not canonized", proposed, assistant-written version: "A creator tries to step away from technical execution, but a single mission becomes three competing approval cards." NL v4, "8. Candidate narrative beats β Offered to the author, not canonized", proposed, assistant-written version: "A later reading or watch-recorded reflection revisits the original review, challenges an interpretation and may lead to another screenwalk." NL v4, "stored transcript turn 134:33" at 134:33 (generated, unverified), proposed, Gemini stored transcript: "Its interruptions became part of the composition." PII v2, "1. Research-Creation and Research Through Design", proposed, assistant enrichment: "What does the recorded encounter contribute as an artwork or methodological artifact, beyond the code and issue tracker it documents?" | None named | The author as filmmaker and Twine writer. | Now: the beats read well and nobody chose them. To exist: the author's own selection, if they make one. | Keep them where they are. An author-chosen beat can be recorded when they return to this material. | Reliability: Version 4 keeps sections 8 and 9 readable at its frozen hash. Agency: The author picks one beat, rewrites it or drops all four. A beat they did not choose is not used. | Story with Continuity | Preserve | no | pending |
Research#
| id and question | source and status | existing issue | beneficiary | tension | possible contribution | smallest proof | circle | suggested action | asks the author now | decision |
|---|---|---|---|---|---|---|---|---|---|---|
| CM-03 For the Concordia proposal, what is the creative work, what is the reflection, and which existing pieces are only precedents? | PI v3, "1. Cinematic Research-Creation β Practice-Led Inquiry", proposed, assistant enrichment: "What is the creative work itself, what does the written reflection establish, and which existing artifacts are precedents rather than the final thesis work?" PI v3, "Reading and Verification Notes", verified_independently, assistant enrichment: "Concordia requests a five-page research-creation proposal and calls its six listed contents suggested elements to include" PI v3, "Results" at 11:58-12:15 (generated, unverified), verified_independently, generated review text: "specific requirement for a five-page research-creation thesis proposal" PI v3, "Emerging Cross-Field Proposition", proposed, author-supplied dialogue and its framing: "The quality of the research is not established simply by the software working or the archive persisting." PII v2, "1. Research-Creation and Research Through Design", proposed, assistant enrichment: "Concordia's Cinematic Arts MFA frames practice-led research-creation as integrating artistic production with critical and theoretical inquiry" | None named | The author as applicant and writer. | Now: a body of work, and readings that keep treating it as already meeting requirements. To exist: the author's own statement of what the thesis work is, from which they writes the five pages. | The author reads F1 to F12 and marks each. No new research is needed before that. | Reliability: Each proposal claim that cites Concordia points to the page's wording on a dated read. Each of F1 to F12 is marked right, wrong or set aside. Agency: The author can state in their own words what the work is and what the reflection is, and says the draft reads as theirs. | Story with Evaluation, Continuity | Explore academically | yes | pending |
| CM-04 Did the Factory reduce coordination work for the creator, or move it into approvals, missing sessions and follow-up prompts? | PII v2, "6. Situated Interaction and the Human Cost of Orchestration", proposed, assistant enrichment: "Did the Factory actually reduce coordination work for the creator, or merely shift that work into approvals, missing sessions and follow-up prompts?" NL v4, "π¬ Evaluation Circle β Evidence and creative experience", proposed, assistant-written version: "Did mission drafting, waiting, duplicate approvals, delayed status, or uncertainty force the creator back inside the operational loop?" NL v4, "6. Near-loop friction ledger β Candidate measurements", observed, assistant-written version: "No measured durations or successful audio exports are claimed here." NL v4, "stored transcript turn 98:16" at 98:16 (generated, unverified), author_reported, Gemini stored transcript: "I had to jump in in the loop to finish the work" NL v4, "stored transcript turn 77:33" at 77:33 (generated, unverified), author_reported, Gemini stored transcript: "there's something that doesn't fit in my understanding of how the connector works" PII v2, "πΈ AvaβMia Reflective Reading β From Fields to Methodology", proposed, assistant enrichment: "how can the Factory preserve creative agency while taking responsibility for the coordination it promises to automate?" | jgwill/Miadi#930 (open) | The author's time and momentum, and anyone relying on the Factory's self-description. | Now: test counts and deployment claims stand for improvement. To exist: a timeline the author can read, with their own marks on which interruptions cost them something. | One timeline for screenwalk 38rsaFfX10g under the existing inquiry, not a new study. | Reliability: Each interval cites a transcript turn checked against the video and a connector receipt, and states its cause or says unknown. Agency: The author reads it and marks which interruptions cost them something and which they wanted. Counts do not replace those marks. | Evaluation with Continuity | Verify source | no | pending |
Stewardship#
| id and question | source and status | existing issue | beneficiary | tension | possible contribution | smallest proof | circle | suggested action | asks the author now | decision |
|---|---|---|---|---|---|---|---|---|---|---|
| CM-05 On what standing may these reviews and the Knowledge Focus Ethics test cite Shawn Wilson? | RR v17, "Grounding Knowledge in Relational Axiology (41:00-47:30)" at 41:00-47:30 (generated, unverified), inferred, generated review text: "Drawing directly from Shawn Wilson's Research Is Ceremony alongside classical philosophical definitions" PI v3, "6. Indigenous Relational Research Methodology β Contextual Research Lead", proposed, assistant enrichment: "His work should therefore be treated as a proposed reading and relational-ethics question, not as scholarship already demonstrated by this screenwalk." NL v4, "3.1. Relational epistemology and research-creation β candidate 21:14β23:35" at 21:14-23:35 (generated, unverified), inferred, assistant-written version: "The discussion draws on the user's reading of Shawn Wilson's Research Is Ceremony" NL v4, "3.1. Relational epistemology and research-creation β candidate 21:14β23:35", proposed, assistant-written version: "Use of ceremony, talking circles, or medicine-wheel structures is not by itself evidence that Miadi is an Indigenous research methodology." | miadisabelle/Etuaptmumk-RSM#281 (open) jgwill/Miadi#871 (open) | The people and communities whose knowledge is cited, the author, and readers of the reviews. | Now: a public review says the work draws directly from Wilson, and another says the citation is only a lead. To exist: a stated standing for each use, decided by people. | Take this up in the circle that exists for it. Nothing here certifies cultural standing. | Reliability: Each of the four parts is marked supported at named pages, or not supported, in GUIDANCE, passing the folder's quote boundary. Agency: The author and the people in relation say whether each use is acceptable, recorded as their words. No machine-issued approval. | Stewardship with Evaluation | Talking Circle or stewardship discussion | yes | pending |
| CM-06 Is it acceptable that reviews the author labels internal, and one naming a faculty member, are publicly listed and readable without sign-in? | NL v4, "9. Related records and boundaries", observed, assistant-written version: "The email to Nicolas Renaud remains an academic correspondence draft, not a completed or sent outcome of this screenwalk." NL v4, "Building the Near-Loop Factory: Friction, Correction, and Relational Inquiry", observed, assistant-written version: "Internal Chimera research-creation screenwalk" NL v4, "πΏ Stewardship Circle β Consent and accountable relationships", proposed, assistant-written version: "Who may preserve a participant's speech, attach it to a public review, synthesize it into voice, or use it to modify a specification?" PI v3, "6. Indigenous Relational Research Methodology β Contextual Research Lead", proposed, assistant enrichment: "What permissions, attributions, and human relationships must be honored before archived observations become a proposal, a public narrative, or a reusable agent instruction?" | jgwill/Miadi#815 (open) | The named person and any participant, then the author. | Now: a sentence about correspondence with a named person is on a public page. The version was approved on a card, and the audit of 2026-11-04 reports that approval views show the first 1,200 characters. To exist: the author's decision on what these pages hold. | The author reads section 9 of Near-Loop v4 and the four pages' reach, then says keep or change. | Reliability: A listing, from the frozen texts, of each named person in the four reviews and each review's reach, repeated after their decision. Agency: The author, and the named person where the author chooses to ask, say what they accept. Recorded as their words. | Stewardship with Continuity | Talking Circle or stewardship discussion | yes | pending |
Engineering#
| id and question | source and status | existing issue | beneficiary | tension | possible contribution | smallest proof | circle | suggested action | asks the author now | decision |
|---|---|---|---|---|---|---|---|---|---|---|
| CM-07 What does transcript-first do today for a released screenwalk, as against what the Part II review says it enforces? | PII v2, "Results" at 87:35-87:55 (generated, unverified), inferred, generated review text: "The connector now enforces transcript capture as the mandatory first ingestion stage, backed by 237 passing tests" PII v2, "Transcript-First Ingestion Architecture (47:05-52:30)" at 49:15-52:30 (generated, unverified), inferred, generated review text: "guaranteeing that raw video transcripts are captured, timestamped, and stored as immutable baseline artifacts" PII v2, "3. Provenance and Evidence Architecture", proposed, assistant enrichment: "nor that a deployed connector is actually configured to process new recordings" PI v3, "Reading and Verification Notes", observed, assistant enrichment: "The timestamps above are inherited from the generated review, not independently transcribed or video-checked here." NL v4, "3. Timestamped aspects β Candidates from review v2", observed, assistant-written version: "not independently verified against the complete video" | jgwill/Miadi#925 (open) jgwill/Miadi#847 (open) | The author, and every later reader who relies on a timestamp. | Now: three of the four frozen reviews have no transcript and the fourth has a generated one. To exist: one released screenwalk whose transcript receipt is earlier than its V1. | Correct the wording around #925 and keep it open. Engineering returns provider options with costs when the author asks. | Reliability: One receipt showing a source-part hash stored before V1 was created, for one real screenwalk. Agency: The author reads that reading and says whether it stays closer to what they said than a video-only V1 does. | Engineering with Evaluation, Stewardship | Fix existing issue | no | pending |
| CM-08 Does anything apply the four Knowledge Focus Ethics criteria before an attention item reaches them? | RR v17, "keypoints by apple", author_reported, author's note: "Current reservations are that agents tend to invent attention inquiry for human, this could help resolve that to clear relevant attention items added to episodes." RR v17, "Results" at 1:02:00-1:04:00 (generated, unverified), inferred, generated review text: "AI inquiry is guided by relational responsibility, epistemic worthiness, and intentional attention rather than raw output optimization" NL v4, "3.2. Cross-model scrutiny and the biases in βrelational platformβ β candidate 25:06β26:00" at 25:06-26:00 (generated, unverified), proposed, assistant-written version: "productivity bias (value reduced to faster output)" | jgwill/Miadi#872 (open) | The author, by receiving fewer invented questions. | Now: agents can still add attention items without answering the test. To exist: items that reach the author having passed it, with the author's own view of whether they were theirs. | Record this receipt on #872 when authorized. This map is a first hand-applied trial of the test: five of twelve rows pass. | Reliability: An attention door refuses an item without the four answers in a test, and one real later item carries for and focus. Agency: After a set of real asks the author marks which were theirs to answer. Those marks measure invention, not a score. | Evaluation with Engineering | Fix existing issue | no | pending |
| CM-09 Did the system formalize dependency-aware delegation, or was the sequencing written by hand in an issue and followed? | PII v2, "Core Aspect β Dependency-Aware Autonomous Agent Delegation (77:20-79:15)" at 77:20-78:30 (generated, unverified), inferred, generated review text: "the system formalizes an automated delegation protocol" PII v2, "Dependency Gating Across Concurrent Worktrees (72:00-93:30)" at 72:00-74:45 (generated, unverified), inferred, generated review text: "downstream mission #926 was held until upstream mission #925 completed" PII v2, "Results" at 77:50-78:30 (generated, unverified), unknown, generated review text: "Codified standing instructions for future agent orchestration" PII v2, "2. Computer-Supported Cooperative Work β Shared Context Across Agents", proposed, assistant enrichment: "A chat instruction that says βwaitβ is not automatically a shared monitoring mechanism." PII v2, "Summary", inferred, generated review text: "transitioning the factory from passive code generation into a self-monitoring, continuous research-and-development runtime" NL v4, "2. Editorial evidence contract β Four different kinds of claims", proposed, assistant-written version: "a mission approved or delivered is not a mission completed." | jgwill/Miadi#926 (closed) jgwill/Miadi#913 (open) | The author, who would otherwise reconnect sessions by hand. | Now: a generated summary says self-monitoring. The issue says otherwise. To exist: the claim marked correct or corrected after reading the recording at the anchor. | Read the recording from 77:20 to 79:15 and search for the instruction text, before anything is built. | Reliability: The passage is read against the recording, and the instruction is found at a named place or marked absent. Agency: The author says whether they want a dependency gate at all, or prefers to hold approval themselves, as #926 allows. | Evaluation with Engineering | Verify source | no | pending |
| CM-10 What stands between a review and the decomposition chain reaching the Factory, as things are? | RR v17, "Post study of this content", author_reported, author's note: "at least separate/decompose the observed screenwalk into what Iβd truely want" NL v4, "2. Editorial evidence contract β Four different kinds of claims", proposed, assistant-written version: "automatic routing from a review through the Factory and Chronicle without repeated manual prompting" NL v4, "Building the Near-Loop Factory: Friction, Correction, and Relational Inquiry", proposed, assistant-written version: "screenwalk_creative_research (not verified as a saved system field)" | jgwill/Miadi#870 (open) jgwill/Miadi#818 (open) jgwill/Miadi#885 (open) jgwill/mia-code#94 (open) | The author, whose stated complaint is that a summary is not what they meant. | Now: a released chain that needs a speaker-labelled transcript no current door produces for these reviews. To exist: one review whose points the author recognizes, delivered through the signed route. | Record on #870 what this read found, and leave its open steps as they are. | Reliability: One signed delivery receipt in the Factory ledger for a chain, with speaker labels checked against the audio. Agency: The author compares the chain's points with their own reading of one review and says which were missed or invented. The 11 of 11 on review 9281cda0 was measured against a hand map, not by the author. | Engineering with Evaluation, Continuity | Fix existing issue | no | pending |
Continuity#
| id and question | source and status | existing issue | beneficiary | tension | possible contribution | smallest proof | circle | suggested action | asks the author now | decision |
|---|---|---|---|---|---|---|---|---|---|---|
| CM-11 How do their post-study corrections on the Reflective Return review reach the next version and the twelve-row table waiting on them? | RR v17, "keypoints by apple", author_reported, author's note: "If that implied in the rest of the content it needs revision" RR v17, "keypoints by apple", author_reported, author's note: "Iβm not slowing down my process." RR v17, "keypoints by apple", author_reported, author's note: "I am simulating it I am enforcing it" RR v17, "Multi-Tool Workflow for Reflective Return (1:10:00-1:15:30)" at 1:10:00-1:15:30 (generated, unverified), inferred, generated review text: "This strategic delay allows human cognition to actively challenge agent outputs before committing structured artifacts" RR v17, "Core Aspect β Relational Axiology in Software Factory Pipelines (1:00:00-1:03:30)" at 1:00:00-1:03:30 (generated, unverified), inferred, generated review text: "ensures project evolution remains strictly accountable to human authorial intent and cultural responsibility" RR v17, "keypoints by apple", author_reported, author's note: "great crappy framing needs reformulation and if the content impkies that this is dangerous assumption" RR v17, "Reflective Return" at 0:01:17, 1:51:38 (generated, unverified), inferred, Apple prompt output: "A practice of strategic delay and revisiting past research to uncover new, evolving directions" RR v17, "Volume Zero Strategy", verified_independently, author's note: "There should also be a ceremony created inside of talking Circle that we need." PII v2, "π Academic References and Source Boundaries β Added Reading", observed, assistant enrichment: "The append-only survey and dialogue are author-reviewable hypotheses, not corrections to V1." PI v3, "π Academic Sources and Provenance β Added to Version 2", observed, assistant enrichment: "Original source claims await separate verification." | jgwill/Miadi#871 (open) jgwill/medicine-wheel#169 (open) avadisabelle/coaia-narrative#57 (open) miadisabelle/asterion#23 (open) | The author, and any reader or agent who takes the Aspects as a true account of their practice. | Now: the author's correction is in the document and the claim they rejected is still there, unchanged, in the part agents read first. To exist: a next version that reads true to them, with the earlier text kept in history. | The author marks the #871 table and the Apple key points, in the ceremony that exists. An agent then prepares version 18 for their approval. | Reliability: The diff of version 18 shows each correction applied, with earlier versions intact and a read-back hash. Agency: The author reads the new Aspects and says they no longer misstate their process. | Continuity with Evaluation, Story | Fix existing issue | yes | pending |
| CM-12 Which episode links in Part I have receipts, and which are only the review's narration? | PI v3, "Results" at 12:55-14:30 (generated, unverified), inferred, generated review text: "establishing cryptographic provenance to episodes 567 and 044 while locking Episode 067" PI v3, "3. Provenance and Knowledge Representation β Lineage Is Not Truth", proposed, assistant enrichment: "Which episode links have machine-verifiable receipts, which are inferred, and which still require a witness or author to confirm their meaning?" PI v3, "Core Aspect β Autonomous Lineage Integrity Recovery (12:55-14:30)" at 12:55-14:30 (generated, unverified), inferred, generated review text: "commits staged research outputs without human intervention" PI v3, "Summary", inferred, generated review text: "autonomously repairs an interrupted mint sequence, establishing verifiable episode lineage across decentralized agent sessions" PI v3, "Results" at 10:50-11:35 (generated, unverified), inferred, generated review text: "NotebookLM successfully surfaces an eighteen-source relational knowledge matrix" PI v3, "Lineage Repair and Episode Ingestion (12:35-13:20)" at 12:35-13:20 (generated, unverified), inferred, generated review text: "Detecting an interrupted minting run where Episode 067 lacked a manifest" PI v3, "Reading and Verification Notes", verified_independently, assistant enrichment: "is not yet linked to this review through the Chronicle review door" NL v4, "9. Related records and boundaries", proposed, assistant-written version: "episodes 553 and 567, subject to cross-checking exact relations" | None named | Whoever returns to Episode 570 or 067 to write the proposal, the author first. | Now: a generated Results point states provenance and a lock, and the survey around it warns against trusting that. To exist: a short ledger for one chain, with each link marked observed, inferred or unverified. | Read 12:35 to 14:30 of the recording against these receipts. Propose links only after that. | Reliability: One source-to-claim ledger, recording to review to manifest to decision, with each state stated. Agency: The author says whether Episode 067's present state, with their draft in a folder without a manifest, is what they intend. | Continuity with Evaluation | Verify source | no | pending |
Existing state of each row#
State words: implemented, tested, deployed, unconfigured, proposed, blocked, unknown. On a fact that is not software, tested means read at its source in this session, and implemented means the record or document exists.
CM-01#
The voice layer exists. Using it inside a shoot as a method, with labelled turns, is only their stated wish.
| component | state | evidence |
|---|---|---|
| Five-voice track: @miadi/voice 0.4.0, voice-client 0.3.0, voice-mcp 0.5.0 | implemented | miadi-chronicle://569 status.md, commit 08b5fd21. run_request:17d0ce6c still shows no submitted result, so this is the session's account. |
| Transcript that keeps an injected voice apart from the person | unknown | The Near-Loop stored transcript names script voices on 45 of 91 turns and never names the person. Checked against no audio. |
| Injection as a planned step of a shoot, with context supplied to the voice | proposed | Their note in the review. No spec or issue read names it. |
Alternative readings:
- The injected voices may matter more as public-facing dialogue than as a shooting aid. The review's Multi-Voice Results point reads them that way.
Contradictions kept:
- The review's Aspects call the stack a deliberate slowdown. Their note says it is not, and also agrees that the tools do slow them. See CM-11.
Uncertainty: No audio was heard in this session. Whether the voices were audible in any recording is inferred from a generated transcript.
Decision gate: The author chooses whether, when and with which voices. Another person's voice needs that person's consent first.
CM-02#
The beats live in review text only. They are not recorded as candidate beats on the connector.
| component | state | evidence |
|---|---|---|
| Beats A to D in the review | proposed | Section 8 of the frozen Near-Loop version. |
| Candidate beat records on the connector | unknown | list_records on this review returned 6 records, none a beat. The author's selection is unknown. |
Alternative readings:
- The interruptions may be incident material rather than composition. The composition line comes from a generated persona script.
Uncertainty: The transcript line is from a script read during the recording, not from the author.
Decision gate: Only the author makes a beat canon. No automatic conversion into an engineering ticket.
CM-03#
Concordia's page was read today. Episode 570 already holds a second reading with twelve findings, written for them and not yet ruled on.
| component | state | evidence |
|---|---|---|
| 5-page proposal, suggested elements, Fall only, December 15 deadline | tested | Fetched and read on 2026-11-04 from the Concordia application page, RC4. |
| Notebook bd094fd8 and its second reading F1 to F12 | implemented | miadi-chronicle://570 captures README, commit 2cf42c73. Its common error: work that could feed the proposal is presented as already meeting a requirement. |
| Proposal draft v3 | implemented | miadi-chronicle://067 draft.v3.md exists. Its folder has no episode.yaml, see CM-12. |
| Which program and which intake the author is applying to | unknown | miadi-chronicle://570 README says Fall 2027 is the notebook's reading, and points to Episode 567's Q2 on MFA or certificate. No answer read. |
Alternative readings:
- The author may be aiming at another program or a later cycle, in which case the date does not apply. The reviews do not settle this.
Contradictions kept:
- Part I says eighteen sources and Episode 570 says twenty-eight, see CM-12.
- Part I's survey calls Wilson a lead, while the private Wilson folder records pages read, see CM-05.
Uncertainty: Whether the author has already read the second reading is unknown. If so, only the marks are owed.
Decision gate: The author decides what is the thesis work and whether to apply. No agent contacts Concordia or a named faculty member.
CM-04#
An Evaluation inquiry already asks this and is pending. The friction ledger in the review holds no measurement.
| component | state | evidence |
|---|---|---|
| inquiry:9f202ba9-1521-49c0-a16e-7678db81423d | proposed | state pending on the connector ledger, circle evaluation. |
| Friction ledger with measured intervals | unknown | The Near-Loop review states no durations were measured. The stored transcript is generated and has no turn from 15:11 to 24:12. |
| Creator-experience records | implemented | observation:57711f75 records joy on 2026-10-31, observation:3a936d50 records not understanding an approval on 2026-10-22. |
| Steering a busy session | blocked | Three authored corrections to this very mission were refused at 21:44 to 21:46Z on 2026-11-04, session_steer_request:c7df8094, 3e28bf29 and d7bb97d2. jgwill/Miadi#930 records it as a P0 and says the author was acting as the scheduler. |
Alternative readings:
- Some interruptions may be the approval boundary they want, not friction. The inquiry itself separates these causes.
Contradictions kept:
- The author recorded joy at reduced manual work on 2026-10-31, and on 2026-11-03 said they had to jump in the loop. Both stand.
Uncertainty: Transcript turns are Gemini's and unverified. Turn 98:16 and turn 77:33 read as their voice by content, not by any label.
Decision gate: The author reads the timeline before any improvement is proposed. The inquiry says no new work starts from it automatically.
CM-05#
A private study folder, a page-grounding issue and a dense-source circle already exist. None has an entry connecting the four-part test to Wilson's pages.
| component | state | evidence |
|---|---|---|
| Private Wilson study folder: INDEX, GUIDANCE, LEDGER | implemented | sources/wilson-2008-research-is-ceremony. Its README keeps page text out of public places. |
| Grounding of the four-part test in pages | proposed | miadisabelle/Etuaptmumk-RSM#281 open with 0 comments. grep finds 'knowledge focus' 0 times in INDEX, GUIDANCE and LEDGER. |
| Dense-source circle | proposed | miadi-circle://circle:1793377035726:dwjgml, delay due 2026-10-30. The wheel returned no ceremony for that circle id on this read. |
Alternative readings:
- Part I's 'not confirmed as read' is scoped to the Episode 570 inquiry. The private folder records pages read, and the Near-Loop review speaks of the author's own reading. These may all hold.
Contradictions kept:
- Reflective Return says drawing directly from Wilson, while Part I says research lead.
- The Near-Loop anchor 21:14-23:35 for their reading falls inside a stretch with no stored transcript turn. Wilson's name appears once in that transcript, at 28:15.
Uncertainty: Whether the words were spoken on video at 41:00-47:30 or 0:51:09 is unverified. The folder's reader for each page is not established here.
Decision gate: People decide. The agent proposes no wording for public use and creates no circle.
CM-06#
All four reviews and all four videos are reachable without any sign-in today. Earlier records hold that person's consent as not cleared.
| component | state | evidence |
|---|---|---|
| Public reach of the four reviews | deployed | Fetched with no token: /raw and /json 200, and all four ids appear in /review/list, /review/index and /review/feed.xml. RC3. |
| Public listing of the four videos | deployed | Each watch page reports isUnlisted false and playability OK, RC5. |
| Consent to quote the named person | blocked | miadi-chronicle://067 HELD section 3 says none of it was cleared with that person. miadi-chronicle://567 script.md line 75 says nothing about the inquiry to that person reaches a public page until the author decides. |
| Private review or source visibility | proposed | PR 927 names private source bundles in the v0 V6 prompt, not applied. |
Alternative readings:
- The author shares reviews publicly on purpose, and 'internal' may mean the kind of recording, not secrecy.
- One mention of a draft email may not be what the earlier rule meant by the inquiry to them. They approved v4 on 2026-11-04.
Contradictions kept:
- miadi-chronicle://567 says nothing about the inquiry reaches a public page until the author decides, while the review is public. The audit of 2026-11-04 reports the card showed 1,200 characters, so whether this sentence was in front of them is unknown.
Uncertainty: A search for four names known from Episodes 067 and 570 was run over these four reviews, and one matched. Other public reviews were not read. Whether the author has already considered this is unknown.
Decision gate: The author decides. This session changes no review, contacts nobody and creates no circle.
CM-07#
The contract is merged, tested and live. The provider is not configured. The review that claims enforcement was itself created without a transcript, seven hours after the merge.
| component | state | evidence |
|---|---|---|
| Reading workflow code | implemented | PR 927 merged 2026-11-04T14:24:32Z, merge 92ffd3b0. |
| Connector tests at HEAD 2ab2fb00 | tested | node --test test/*.test.mjs, no rebuild: 260 passed, 0 failed, RC2. A synthetic pipeline only, per the PR. |
| Connector 0.1.20 live | deployed | /health reports 0.1.20. get_capabilities reports contract transcript-first-v1. |
| Transcript provider | unconfigured | get_capabilities: provider_runtime not_configured. |
| Atomic import to the review service | blocked | get_capabilities: blocked_until_authenticated_sha256_cas_v1_handshake. The v0 V6 prompt is not applied, per PR 927. |
| The create door used for Part II | deployed | review_operation_request:adcf13c0 created v1 at 21:07:00Z by gemini-3.7-flash. Its client read reports has_transcript false. |
Alternative readings:
- The create door may stay deliberately separate from the new path. #925 allows a bypass only with a recorded author choice and a transcript_missing status. Neither appears on this review.
Contradictions kept:
- Part II Results say the connector enforces transcript capture as the mandatory first stage. Capabilities and PR 927 say live processing stays blocked.
Uncertainty: Whether the V1 generator used captions internally is unknown. No stored transcript exists for it.
Decision gate: Provider, budget and source rights are the author's, per #925 and #847. Merging or releasing needs its own authorization.
CM-08#
The test is in the schema and tested. No door, skill or stored item uses it. This answers the first step of #872.
| component | state | evidence |
|---|---|---|
| KNOWLEDGE_FOCUS_CRITERIA and knowledgeFocusVerdict | implemented | packages/episodic-memory-schema/src/attention.ts, schema 0.17.0 commit f2555927, now 0.17.1. |
| Schema attention tests | tested | node --test test/attention.test.mjs: 6 passed, 0 failed, RC2. |
| Any caller of the verdict | unconfigured | grep over app, lib, packages, skills, the kit and /etc/claude-code/skills finds only the schema, its README and its test. |
| Items that carry the fields | unconfigured | 36 items in 11 attention.json files: 0 with for, 0 with focus. 4 were asked after schema 0.17.0. |
| A package named @miadi/attention | unknown | @miadi/attention-core 0.1.1 and @miadi/attention-ui 0.3.1 exist. No @miadi/attention. Whether the author means these is theirs to say. |
Alternative readings:
- Agents may answer the four by hand with no trace in code. No item's focus field shows this.
Contradictions kept:
- The review's Results name three criteria plus an exclusion and call it four-part. The schema's fourth is the exclusion. Chimera's own wording at 1:02:00-1:04:00 was not retrieved.
Uncertainty: Skills outside the searched folders and agents' private instructions were not read.
Decision gate: Enforcing at a door is a behaviour change that needs their authorization. Package names are the author's.
CM-09#
The order held on the record, and the gate is prose in an issue. No dependency mechanism or codified instruction was found.
| component | state | evidence |
|---|---|---|
| Merge order #925 then #926 | tested | PR 927 merged 14:24:32Z, PR 928 merged 14:53:50Z, read through gh. |
| Written sequencing gate | implemented | jgwill/Miadi#926 body, Mandatory sequencing gate. It also states approval queues an agent immediately and is not native dependency scheduling. |
| Dependency field or monitor in code | unknown | grep over packages/connector/src and packages/factory-runner/src for depends_on, dependency_gate, blocked_by and monitor found nothing. Other words were not searched. |
| Codified standing instruction | unknown | grep over the kit, /etc/claude-code/skills, skills and the two packages for the review's phrases found nothing. ChatGPT's own memory is not readable here. |
Alternative readings:
- The review may be describing instructions given in chat during the recording, which would be true as a practice and false as a system property.
Contradictions kept:
- Part II's Core Aspect says automated monitoring. jgwill/Miadi#926 says not to claim native dependency scheduling.
Uncertainty: Watch page listed no caption track for this video on 2026-11-04. No transcript exists to check against.
Decision gate: A new mechanism would be a separate mission that the author authorizes. This row does not propose one.
CM-10#
The chain is released and its verifier passes. It has not reached Factory dispatch, and it cannot read any of these four reviews as they stand.
| component | state | evidence |
|---|---|---|
| miaco decompose review | implemented | jgwill/mia-code 7d5dbd7, tags from miaco-v0.20.7, installed 0.20.14. |
| Chain contract verifier | tested | node miaco/scripts/verify-screenwalk-review-contract.mjs, exit 0, RC2. |
| Delivery to the Factory intake | proposed | factoryIntakeRoute returns delivery named-not-called, miaco/src/screenwalk-review.ts:100. No signed delivery receipt exists. |
| Chain input on the four reviews | blocked | Three have no stored transcript, which the code refuses. On the fourth, parseTranscript returned 0 turns because its lines are not in the [time] Speaker N: form. |
| Review-kind route and catalog | deployed | GET /api/factory/review-workflow on :3335 lists five kinds. 17 route tests pass, RC2. Workflow is null on all four reviews. The v0 UI is not accepted, jgwill/Miadi#885. |
| Catalog note on the chain | unknown | lib/factory-review-workflow.ts:126 says not in a released miaco yet, while the tag shows it is. The note is older than the release or was not updated. |
Alternative readings:
- A transcript generated by another path, in Speaker N form, may parse. The chain did parse review 9281cda0 by its issue's account. Only the current stored forms were tested here.
Contradictions kept:
- Near-Loop proposes kind screenwalk_creative_research. The service stores explainer-feedback, and the catalog has neither that proposed kind nor narrative_continuity_inquiry.
Uncertainty: The parser was run on one transcript. Review 9281cda0's transcript was not read here.
Decision gate: Dispatch stays off until the author approves. The sibling or kind decision is listed on #870 for its owner.
CM-11#
Their notes sit beside the unchanged generated text. The table, the ceremony and the six issues wait on their marks.
| component | state | evidence |
|---|---|---|
| Review version 17, latest | implemented | Frozen version. The Aspects keep the strategic delay sentence, and the post-study holds their correction. |
| Twelve-row table | proposed | jgwill/Miadi#871 open, 0 comments, review step not done, date not set by the issue. |
| Ceremony for the review | implemented | miadi-ceremony://0ef2f473-259b-468c-9662-a9632763658d exists. 0 of 295 wheel beats name it. |
| Reflection layer spec | proposed | jgwill/medicine-wheel#169 open, 0 comments. |
| Holder version | implemented | miadi-chronicle://563 holds version 16 of this review, per get_context. |
Alternative readings:
- Strategic delay may be real at another level. coaia-narrative's delayed resolution and their delayed research return are a different act from slowing a tool chain. #871 row 3 rests on that match, which is a seat's reading.
Contradictions kept:
- The Aspects say deliberately slow down, and the author replies they are not. The author also says the tools do slow them, not deliberately.
- The Core Aspect says the system ensures accountability, and the author says they are simulating and enforcing it.
Uncertainty: Whether the author considers the Apple key-point notes finished is unknown. Several have empty notes.
Decision gate: Their marks first. Publishing version 18 needs their approval of the exact text.
CM-12#
The lineage of Episode 570 to 567 and 044 is on the wheel. Locking Episode 067 and cryptographic provenance have no receipt read. Three of the four reviews are held by no episode.
| component | state | evidence |
|---|---|---|
| miadi-chronicle://570 lineage to 567 and 044 | tested | Wheel edges continues_from and relates_to, and episode.yaml lineage, read 2026-11-04. |
| miadi-chronicle://570 commits | implemented | Five commits by jgi on 2026-11-03: two at 21:59 and three from 22:58 to 23:06, local time. |
| miadi-chronicle://067 lock | unknown | Folder has no episode.yaml. The wheel answered with no node for it. Its only commit that day adds a resume script at 11:35. No lock found. |
| Review to episode links | proposed | 0 wheel edges to Part I, Part II or Near-Loop. Only 2c8c8f1d is held, by miadi-chronicle://563. link:66304382 ties Part II to Part I on the connector. |
| Cryptographic provenance | unknown | Git commit hashes exist. No signature or other mechanism was read. |
Alternative readings:
- Eighteen may be right for a moment before the 2026-11-03 additions, since Episode 570's README lists sources added in three stages reaching twenty-eight.
- Locking may name something shown on screen that left no record here.
- Five verified stages may paraphrase the chronicle's five-stage gate.
Contradictions kept:
- Part I says without human intervention. Its own Aspects say the operator instructs the assistant, and the commits carry jgi as author.
- Two Episode 570 commits are stamped 21:59, before the 22:02 in the screenwalk's name. If the stamp marks the start of recording, those commits precede it. The stamp's meaning for this recording is unverified.
Uncertainty: The recording was not watched. The wheel's empty answer for Episode 067 was read through one node id.
Decision gate: Linking a review to an episode is an approved act. Adoption of Episode 067 and minting stay out of this session.