Reference · Feature stories

Feature stories

A thirty-second story for each canonical feature: the pain it answers, the position it takes, one concrete example with its evidence, and the next step. Each one is narrated, captioned, and transcribed, and each one links to the guide that holds the full configuration.

How to read a story

Every story follows the same thirty seconds. The first six seconds name the pain. The next seven say what RepoOps does about it and why it takes that position. The next ten show one concrete action or configuration and the evidence it produces. The last seven say what that evidence establishes and what to do next. The visuals are the website's own components at video size, so the panel you see in a story is the panel you meet in the product and on its guide.

Every example is synthetic and says so on screen. A story shows an illustrative case, never a customer result, and it never claims what the evidence cannot establish: a linked session helps establish contribution rather than cause, a delivered lesson is not a prevented recurrence, and a recurrence that was not assessable reads as unknown rather than as success.

Captions come from the same timing file as the narration, so what appears on screen is what is being said at that moment. The transcript under each player is the text alternative, one line per caption with its start time. Press play to start a story; nothing plays on its own and nothing plays with sound until you ask.

About the narration

Each story records its narration provenance in the manifest beside the video: the provider, the voice, whether the voice is provisional, and the license note. A provisional voice means the build machine's speech platform read the reviewed script so the timing, the captions and the visuals could be checked; the approved narration source is an operator decision recorded on the ledger, and a story is re-rendered from the same script when it lands. Nothing about the words changes between the two.

The manifest also records the versions a render was made from: the product release, the composition, the theme values, the story script, the narration track and the encoded output, each by content hash. A story whose guide changes gets re-rendered, and the hashes say whether that happened.

68 stories

A number you can walk back to the work

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A dashboard shows dollars saved.
  2. 0:02 Nothing shows the work behind the number.
  3. 0:06 A counter is not evidence.
  4. 0:08 The ledger tells each loop as one sentence.
  5. 0:13 Every hop carries the confidence band its producer recorded.
  6. 0:17 Dollars saved is the tracked cost of the session that introduced the defect.
  7. 0:23 Open loops name themselves.
  8. 0:25 Where the history is thin, it reads not yet measurable.

Synthetic example. Read the guide

A clean result has to say what ran

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 An agent opened a branch. It looks clean.
  2. 0:03 Nothing has checked it yet.
  3. 0:06 RepoOps runs three checks on the developer's machine.
  4. 0:09 Each result names what ran.
  5. 0:13 A package the agent invented reads hallucinated.
  6. 0:16 An unreachable registry reads unverified, and a gate that is off says nothing was checked.
  7. 0:23 Teams see metadata only.
  8. 0:25 The secret never leaves the machine.

Synthetic example. Read the guide

Which run went wrong, and what it cost

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Eight agent runs finished overnight.
  2. 0:02 The file does not say which one hurt.
  3. 0:06 RepoOps reads the outcome git and CI already recorded.
  4. 0:10 A revert outranks a failed check.
  5. 0:13 Open the run and the waterfall shows its shape, turn by turn.
  6. 0:17 Cost-ranked steps name the call that burned the budget.
  7. 0:23 Label it yourself, pass or fail.
  8. 0:26 That label is a record, not prevention.

Synthetic example. Read the guide

Measure the saving, not the forecast

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The model bill rose.
  2. 0:01 Nothing on it says which call did it.
  3. 0:06 A forecast is not a saving.
  4. 0:08 RepoOps measures cost per call before and after.
  5. 0:13 Seven days each side, five calls minimum.
  6. 0:16 A change that cost more is marked regressed, and the tab says so.
  7. 0:23 Then check your estimate against the Anthropic bill.
  8. 0:26 Decide on the measured number.

Synthetic example. Read the guide

Ask a bounded audit question

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 An event happened.
  2. 0:01 A timestamp alone cannot answer who acted or what changed.
  3. 0:06 Filter by actor and action first, then narrow the time window and repository.
  4. 0:13 RepoOps shows the mirrored envelope's actor, account, action, and bounded payload.
  5. 0:18 The CSV applies the same filters and inclusive dates you inspected.
  6. 0:23 Keep the filtered record, then investigate the source event in its context.

Synthetic example. Read the guide

A merged fix is not a recovered service

Read the guide. Product version RepoOps main at 509e8e8ad (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A fix arrives as a pull request. Nobody has proved it yet.
  2. 0:06 Five checks run first.
  3. 0:08 The new test fails before the fix and passes after.
  4. 0:13 Open the Fix section: the diff, each check, and the approval record.
  5. 0:17 Approve runs every check again before the merge.
  6. 0:23 A merge is not recovery.
  7. 0:25 The case keeps a recovery window and the rollback on record.

Synthetic example. Read the guide

Check the bill against your own records

Read the guide. Product version RepoOps main at 93f5ec71b (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The invoice arrives as one total.
  2. 0:02 Nobody recomputes what it should have been.
  3. 0:06 RepoOps prices your own token counts against the rate card.
  4. 0:10 Then it compares, day by day.
  5. 0:13 Ten detectors name what they found, with both numbers.
  6. 0:17 A day it cannot check reads not checked, never clean.
  7. 0:23 Export the evidence, or draft the dispute.
  8. 0:26 Billing Guard detects; it never caps spend.

Synthetic example. Read the guide

Read the source, not the summary

Read the guide. Product version RepoOps main at 509e8e8ad (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 You know the brain answered this once.
  2. 0:02 Nobody can name the file.
  3. 0:06 RepoOps searches the markdown and cites it.
  4. 0:09 Lexical ranking needs no model download or key.
  5. 0:13 Every hit carries the file, the heading and the line.
  6. 0:16 A counting question answers by SQL, and shows it.
  7. 0:23 Open the source and judge it yourself.
  8. 0:25 Save the answer as a decision.

Synthetic example. Read the guide

Separate inherited rules from repository facts

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A new repository has no memory of the decisions its next session needs.
  2. 0:06 Start with inherited discipline, then separate it from facts found in this repository.
  3. 0:13 The prompt asks the agent to inspect the stack and preserve existing files.
  4. 0:17 Its report separates inherited content from repo facts.
  5. 0:23 Review the diff before keeping it.
  6. 0:25 A prompt is not a verified install.

Synthetic example. Read the guide

A score that says what it did not measure

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A new brain scored twenty-five.
  2. 0:02 Nothing had been measured yet.
  3. 0:06 Average only what you measured.
  4. 0:08 A dimension with no data reports a dash, not zero.
  5. 0:13 Four sub-scores, and the composite says how many it covered.
  6. 0:17 Expired proposals are excluded, not rejections.
  7. 0:23 A dash is a question, not a grade.
  8. 0:26 Fix the worst measured score.

Synthetic example. Read the guide

See who is standing on a decision

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 You are about to change a decision.
  2. 0:02 Who else is standing on it?
  3. 0:06 RepoOps reads every link in the brain and shows both directions.
  4. 0:10 No model, no guess.
  5. 0:13 Each row names the file, the line and the snippet.
  6. 0:16 Files past the caps go unread, so the totals are a floor.
  7. 0:23 Read who cites it, then change it.
  8. 0:25 The guide covers the caps.

Synthetic example. Read the guide

What your brain learned last night

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Your agent relearns the same lesson every week.
  2. 0:03 Nothing wrote it down.
  3. 0:06 Each night RepoOps proposes entries from the week's work.
  4. 0:09 Confidence is the model's own claim.
  5. 0:13 Each card names the signal that triggered it and the file it would join.
  6. 0:17 Accept, edit, or reject; the reject is archived.
  7. 0:23 Accepted text lands in the file your agents read next session.
  8. 0:27 Set the caps.

Synthetic example. Read the guide

See what the next session will load

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-15.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A session starts cold.
  2. 0:02 Last week's errors sit in a file nobody reopens.
  3. 0:06 RepoOps ranks errors and decisions against the files in flight.
  4. 0:10 You see the list first.
  5. 0:13 Each row shows its score.
  6. 0:15 Set the depth, zero to fifty; the same number bounds what your next session loads.
  7. 0:23 Check the ranking before you trust it.
  8. 0:25 The guide names the two terms.

Synthetic example. Read the guide

Optional collectors that say what they cannot prove

Read the guide. Product version RepoOps main at ddbee985c (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A browser chat has no repository behind it.
  2. 0:03 A guess would be worse than none.
  3. 0:06 RepoOps keeps it unassigned,
  4. 0:08 and the extension talks only through native messaging.
  5. 0:13 All three browser adapters are unverified against live traffic.
  6. 0:17 Token counts are estimates, never a bill.
  7. 0:23 The optional Tap counts each dropped copy,
  8. 0:26 while the request still goes through.

Synthetic example. Read the guide

Which zero is real

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Three hosts read zero.
  2. 0:02 Quiet host, or a parser gone blind?
  3. 0:06 A blind adapter sends nothing, so every host reports its verdict.
  4. 0:10 Silence is not health.
  5. 0:13 Gemini reads Not reading this host: twelve requests matched, none parsed.
  6. 0:18 Its zeros are a floor, and tokens read about, never exact.
  7. 0:23 Read the verdict before the number.
  8. 0:25 Nothing here leaves your machine.

Synthetic example. Read the guide

Take the return point before the risk

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 An agent changed tracked files.
  2. 0:02 Your new untracked file sits outside the snapshot.
  3. 0:06 Create the checkpoint before the risky run, then treat restore as a write.
  4. 0:13 RepoOps keeps an annotated tag and checks git status.
  5. 0:16 Force discards tracked work only after you type the repo id.
  6. 0:23 Restore the captured tree.
  7. 0:25 Branch history and untracked files stay outside the claim.

Synthetic example. Read the guide

The job the bill will not name

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The build bill moved.
  2. 0:01 The invoice names a total, never the job.
  3. 0:06 So measure each job, and round it up to the minute the way GitHub bills.
  4. 0:13 A matrix collapses into one row.
  5. 0:15 Eight shards read as one job, so the ranking stops hiding the dearest thing here.
  6. 0:23 This number is modeled, not billed, and the page says so above it.

Synthetic example. Read the guide

Ask which of the ten controls ran

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A benchmark row shows a percentage.
  2. 0:02 Nothing on it says what was checked.
  3. 0:06 RepoOps grades ten controls per run.
  4. 0:09 A control nobody ran never reads as passed.
  5. 0:13 The claim card names each control, its status, and the reason.
  6. 0:17 The headline sentence is derived from those fields, so it cannot drift.
  7. 0:23 Read the missing list, not the number.
  8. 0:25 Then score ours the same way.

Synthetic example. Read the guide

The env var nobody declared

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 It works on your machine.
  2. 0:02 Prod boots with a variable nobody declared.
  3. 0:06 Compare what the code reads with what the env files declare.
  4. 0:10 Names, never values.
  5. 0:13 Each finding names the file and line, the variable, and the fix.
  6. 0:17 A clean result means these checks did not fire.
  7. 0:23 Fix the declaration before the deploy.
  8. 0:25 The guide covers the five checks.

Synthetic example. Read the guide

One vault for the team's service secrets

Read the guide. Product version RepoOps main at 93f5ec71b (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The same token sits in five env files.
  2. 0:03 Nobody knows who holds it.
  3. 0:06 RepoOps keeps it in one encrypted vault.
  4. 0:09 Reach is a choice the owner makes.
  5. 0:13 Every member sees the mask and the status, never the secret.
  6. 0:17 A test says whether the provider answered, or only that it decrypts.
  7. 0:23 Machines pull it; every pull is audited.
  8. 0:26 The guide covers scope and reach.

Synthetic example. Read the guide

A score that points back to evidence

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A hundred-point score can look precise while hiding the habit behind it.
  2. 0:06 Treat the score as an index: inspect each deduction and its evidence before changing behavior.
  3. 0:13 RepoOps names the rule, its severity, the evidence and the fix.
  4. 0:17 The points come from this repository's local telemetry window.
  5. 0:23 Change one habit, then compare the next measured window before judging progress.

Synthetic example. Read the guide

Read the sync line before you trust the screen

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-15.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 You open a second laptop.
  2. 0:02 Did the brain come with you?
  3. 0:06 RepoOps says which it is.
  4. 0:08 Local-only, or last synced three minutes ago on this machine.
  5. 0:13 One screen: sessions per device, the newest lessons, and cost tied to the merged pull request that spent it, with its confidence.
  6. 0:23 Cost it cannot tie to work stays unattributed.
  7. 0:26 Read the sync line first.

Synthetic example. Read the guide

A control that says what it holds

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A control reads armed.
  2. 0:02 Would it hold a merge, or only say so?
  3. 0:06 Advisory names itself on the check run.
  4. 0:08 Only merge hold, in blocking mode, fails it.
  5. 0:13 The check run names each armed control and what held the merge.
  6. 0:16 Unreadable state? It says so and blocks nothing.
  7. 0:23 Arm advisory first.
  8. 0:25 Escalate merge hold on purpose, and disarm any time.

Synthetic example. Read the guide

Do not trust a frozen green flag

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A dead daemon cannot update the green running flag it reported before failing.
  2. 0:06 Judge liveness from cloud receipt time, then inspect each pipeline timestamp and quiet reason separately.
  3. 0:13 After five and a half minutes of silence, a device reads stale.
  4. 0:17 Telemetry push and brain publish get separate columns.
  5. 0:23 Restart the right device; do not call an old heartbeat healthy.

Synthetic example. Read the guide

One host, many repository brains

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A dashboard copy per repository sounds quick, but that portable host is unshipped.
  2. 0:06 Run one supported RepoOps host, then track repositories as content instead.
  3. 0:13 The live store records each repo, and the mirror reads its brain.
  4. 0:17 Missing markdown renders a placeholder until memory is set up.
  5. 0:23 Choose the repo, read the source, and leave portable hosting marked unsupported.

Synthetic example. Read the guide

A transcript request waits for your answer

Read the guide. Product version RepoOps main at 93f5ec71b (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 An incident points at your session.
  2. 0:02 Your team owner asks to read it.
  3. 0:06 It lands on your machine, and no switch can answer for you.
  4. 0:13 Untick what you withhold, and the scrubber counts what it removes.
  5. 0:17 The button says what will leave, and a denial needs a reason.
  6. 0:23 Revoke deletes the stored copy.
  7. 0:25 The Reads column shows what was already read.

Synthetic example. Read the guide

The call, and why it was made

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Six months on, nobody remembers why.
  2. 0:03 The reasoning died in a merge.
  3. 0:06 A log is trustworthy only if nothing writes to it unseen.
  4. 0:10 Machine entries arrive as cards.
  5. 0:13 High and medium cards drain nightly, capped and logged.
  6. 0:16 A card nobody decides is archived, never deleted, and your rejection stands.
  7. 0:23 Read the call, then the reasoning.
  8. 0:25 The log says who wrote each line.

Synthetic example. Read the guide

Write down what done means before the loop runs

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A loop runs every night.
  2. 0:02 Nobody wrote down what done would look like.
  3. 0:06 Declare the goal, the check that proves it, and when to stop.
  4. 0:13 RepoOps reads the contract and names every missing field.
  5. 0:16 Runs sit beside it, so you judge them against what was declared.
  6. 0:23 Contract first. Then every run has something to answer to.
  7. 0:27 RepoOps never runs it.

Synthetic example. Read the guide

Judge the change, not the repository

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 An agent wrote the change.
  2. 0:02 Which of its added lines carry new risk?
  3. 0:06 RepoOps reviews only the lines this diff adds,
  4. 0:09 and it makes no model call.
  5. 0:13 Each finding names the file, the line, the pass and its reason.
  6. 0:17 A clean result still says which brain guards ran.
  7. 0:23 Decide on the line, not the whole repository.
  8. 0:26 The guide covers guards.

Synthetic example. Read the guide

The rule you wrote, and whether it held

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A defect gets fixed.
  2. 0:02 The reason leaves with the branch.
  3. 0:06 RepoOps hashes the prevention rule you wrote.
  4. 0:09 Two entries, one hash, means the rule failed.
  5. 0:13 The tab traces each entry to the commit, the session and the prompt.
  6. 0:17 A weaker match says possibly, and never counts toward attribution.
  7. 0:23 Question the rule, not the person.
  8. 0:26 Nothing reaches the manual without you.

Synthetic example. Read the guide

Map the repo before judging the code

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 AI wrote the code.
  2. 0:01 You still need to understand what is really there.
  3. 0:06 Map the tracked tree first, then explain one file or route in its context.
  4. 0:13 RepoOps shows routes, modules, imports, exports, and file roles.
  5. 0:19 The badge says whether a model or static parsing wrote it.
  6. 0:23 Read the evidence, then decide where to inspect the source next yourself.

Synthetic example. Read the guide

Search what is pushed, not what you remember

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-15.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A reviewer quotes a path.
  2. 0:02 You track four repos and none is open.
  3. 0:06 RepoOps indexes paths and first lines across your repos.
  4. 0:10 From the mirror, not your editor.
  5. 0:13 Type part of the name.
  6. 0:14 Every match lists its path, first line, size and repo, path hits first.
  7. 0:20 Nothing leaves the machine.
  8. 0:23 Open it, or note the repo.
  9. 0:25 Names and first lines, not content.

Synthetic example. Read the guide

A setup that checks itself

Read the guide. Product version RepoOps main at 93f5ec71b (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Setup finished. Every step reads green.
  2. 0:04 Did anything land on this machine?
  3. 0:06 Every step declares what its result must satisfy.
  4. 0:09 A call that returned is not proof.
  5. 0:13 A key Anthropic rejects stops the run and writes nothing.
  6. 0:16 A repo nobody counted reads not counted yet, never zero.
  7. 0:23 Fix it and resume from that step. Earlier work stays.
  8. 0:27 Then Today shows what it found.

Synthetic example. Read the guide

What the fleet did, and what it could not measure

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Agents run on machines nobody watches.
  2. 0:03 The board still shows a number.
  3. 0:06 FleetView folds what already shipped.
  4. 0:08 It captures nothing new and fills no gap with zero.
  5. 0:13 A run nobody priced reads not available.
  6. 0:16 Unclassified work keeps its own bucket, and dormant controls show what they would have blocked.
  7. 0:23 Read the gaps, then arm a control.
  8. 0:25 FleetView never flips a flag.

Synthetic example. Read the guide

A clean count needs measured evidence

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A green posture can hide a ledger nobody verified or evidence never captured.
  2. 0:06 Start with coverage and chain integrity, then interpret policy, egress, and alerts.
  3. 0:13 RepoOps shows each repository's ledger, redaction and policy violations.
  4. 0:18 Then file changes, egress paths and semantic-hold turns.
  5. 0:23 Export local evidence only after every missing or unmeasured state has a name.

Synthetic example. Read the guide

Trace the change one edge at a time

Read the guide. Product version RepoOps main at 509e8e8ad (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 An alert names a line. Someone has to find the change behind it.
  2. 0:06 Follow the deploy, the commit and the session.
  3. 0:09 Each edge names its mechanism and confidence.
  4. 0:13 The case shows what was captured. A partial transcript reads partial.
  5. 0:18 A matched session stays a candidate until someone reviews it.
  6. 0:23 An owner can ask the enrolled installation for the missing transcript.
  7. 0:27 Offline, the request waits.

Synthetic example. Read the guide

A request is not a result

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A detector held an agent's call.
  2. 0:02 The record is on the queue, undecided.
  3. 0:06 Read the legs and the held call first.
  4. 0:08 Then approve or deny, as a second person.
  5. 0:13 Request containment records a request.
  6. 0:15 The desktop daemon revokes the token and reports each leg; one that did not finish reads contain failed.
  7. 0:23 Decide on the record. Anchor the decision.
  8. 0:26 The guide covers the flags.

Synthetic example. Read the guide

A lesson that can check itself

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The same mistake comes back.
  2. 0:02 Someone already wrote that lesson down last time.
  3. 0:06 A note in a file stops nothing.
  4. 0:08 RepoOps gives a lesson a checkable guard.
  5. 0:13 Every guard starts advisory.
  6. 0:15 Three clean catches, no false positives, a clean replay.
  7. 0:19 Then a person may let one block a build.
  8. 0:23 Recurrence is read from later captured sessions, never assumed.
  9. 0:27 The rate can fall.

Synthetic example. Read the guide

Billed and measured, never summed

Read the guide. Product version RepoOps main at 0b397c973 (after v0.3.2, with LDG-1011 part 1); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The provider billed one figure. This machine measured another.
  2. 0:06 Different scopes, so the page never adds them.
  3. 0:09 Billing Guard compares them day by day.
  4. 0:13 Every figure opens its receipts.
  5. 0:15 An unknown rate is counted, not priced.
  6. 0:18 Validation runs on this machine count too.
  7. 0:23 At the budget, builds, validation runs and schedules wait.
  8. 0:27 Provider spend is never capped.

Synthetic example. Read the guide

A page that says how old it is

Read the guide. Product version RepoOps main at 509e8e8ad (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 You open the app, and every page starts reading from scratch.
  2. 0:06 The capture service prepares each page's first read,
  3. 0:09 and the page says how old it is.
  4. 0:13 Close the window and capture keeps running; ten minutes later the server stops.
  5. 0:18 A stopped daemon is restarted, and a crash loop is named.
  6. 0:23 Rolling back checks the database first,
  7. 0:25 then pauses updates until you resume them.

Synthetic example. Read the guide

Review repository access before changing it

Read the guide. Product version RepoOps managed access PR 4753 at b4b446f24; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A failed evidence check does not remove repository access.
  2. 0:06 The App needs Administration permission.
  3. 0:08 An owner chooses the restriction and grace period.
  4. 0:13 Preview affected collaborators, then confirm that list.
  5. 0:17 Changed eligibility stops stale previews. Admins and exceptions stay protected.
  6. 0:23 Review the audit record and restore previous access.
  7. 0:26 Restoration verifies the original GitHub account.

Synthetic example. Read the guide

Know whether the evidence arrived

Read the guide. Product version RepoOps main at 93f5ec71b (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A merged change names a session.
  2. 0:02 Did its evidence ever reach your team?
  3. 0:06 Publish a required policy.
  4. 0:08 Each developer accepts it on their own installation.
  5. 0:13 Connections shows each installation's last receipt and unsent backlog.
  6. 0:17 On a case, Retrieve missing evidence queues a request the device collects on its next poll.
  7. 0:23 A pull request check flags commits without verified evidence.
  8. 0:27 Work outside a pull request stays unseen.

Synthetic example. Read the guide

A saved lesson is not a prevented incident

Read the guide. Product version RepoOps main at 6e044539b (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A lesson was written months ago. Did it change anything?
  2. 0:06 Open the case on its Prevention section.
  3. 0:08 Each delivery, use and guard run is a receipt.
  4. 0:13 The summary shows caught over assessed, with the control version.
  5. 0:17 Too few attempts reads inconclusive, not a rate.
  6. 0:23 If the defect comes back, the case reopens,
  7. 0:26 and the lesson is marked for revision.

Synthetic example. Read the guide

A memory claim you can check

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Your agent remembers.
  2. 0:01 Proving that to someone else is the hard part.
  3. 0:06 Read the fingerprint, not the promise.
  4. 0:09 Any edit to the knowledge changes the hash.
  5. 0:13 Every item carries its own content hash.
  6. 0:16 An item naming a secret or a migration is dropped, and the export names it.
  7. 0:23 Lineage stays empty until you graft.
  8. 0:25 An empty chain is an answer.

Synthetic example. Read the guide

Two numbers that must never be added

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Six providers, six dashboards.
  2. 0:03 So someone adds them up and guesses the total.
  3. 0:06 RepoOps shows two numbers instead of one.
  4. 0:09 The bill, and what this machine saw.
  5. 0:13 Each provider carries a precision band: per-token, day-level, or per-call.
  6. 0:18 A provider you never connected reads not connected, never zero dollars.
  7. 0:23 Read the number and its band.
  8. 0:25 Billing Guard is where you dispute it.

Synthetic example. Read the guide

A brain you can open as a file

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A tool remembers something about you.
  2. 0:02 You cannot open the file it read.
  3. 0:06 RepoOps keeps your brain as files.
  4. 0:08 A capture waits as a proposal until you confirm.
  5. 0:13 Ask a question and the answer lists the source paths.
  6. 0:16 Without a key you get the matching files and no written answer.
  7. 0:23 Confirm what is true, discard the rest.
  8. 0:26 The guide covers the nightly brief.

Synthetic example. Read the guide

Count the repos before you promote a rule

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The same mistake happens in two repositories.
  2. 0:03 Nobody sees the pair.
  3. 0:06 Count the repositories before you promote a rule.
  4. 0:09 Two that wrote it separately is evidence.
  5. 0:13 RepoOps groups brain headings across your repositories.
  6. 0:17 A title in two or more repos is established, and you see each repo's wording.
  7. 0:23 Move the lesson with a pull request you review.
  8. 0:26 The count is evidence.

Synthetic example. Read the guide

A signal you can trace to its repository

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A metric spikes in production.
  2. 0:02 Nobody can say which change did it.
  3. 0:06 Collect beside the service, not on a laptop.
  4. 0:09 One approved workload exchanges a ten-minute token.
  5. 0:13 Each card keeps the collector's own source, time and release.
  6. 0:17 The reported session reads unverified, because nothing has verified it.
  7. 0:23 Investigate the change before judging the agent.
  8. 0:26 The record says who reported what.

Synthetic example. Read the guide

The reasoning the squash keeps

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A change merged three weeks ago.
  2. 0:02 The diff survived. The reasoning did not.
  3. 0:06 Write the record on the branch before the PR opens.
  4. 0:09 The squash merge keeps it.
  5. 0:13 The tab indexes every record, newest number first, and filters as you type.
  6. 0:18 CI blocks a pull request that carries none.
  7. 0:23 Read the record before you judge the change.
  8. 0:25 Archived ones stay findable.

Synthetic example. Read the guide

Use a prompt for judgment, not installation

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A broad setup prompt can turn one generic recipe into a repo-wide diff.
  2. 0:06 Start with deterministic setup. Use the prompt only for choices that need judgment.
  3. 0:13 The prompt asks an agent to inspect the stack and mark conditional files.
  4. 0:17 Then it asks for a branch and a reviewable pull request.
  5. 0:23 Review the diff. A prompt is guidance, not proof that setup worked.

Synthetic example. Read the guide

Inventory is access, not coverage

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A repository row can look monitored before any machine has reported from it.
  2. 0:06 Treat GitHub access and reporting coverage as separate facts, then reconcile their keys.
  3. 0:13 RepoOps joins GitHub inventory with telemetry, brain, cost, and current risk stores.
  4. 0:19 Owners and admins link local slugs; gaps stay blank.
  5. 0:23 Open the repository, verify scope, then investigate whichever source is still missing.

Synthetic example. Read the guide

Capture where it happened. Build only when a person says so.

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-15.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A bug gets mentioned in chat.
  2. 0:02 By Friday nobody remembers which tab.
  3. 0:06 Submit from the tab you are on.
  4. 0:08 RepoOps captures the tab, subtab and URL.
  5. 0:13 You promote it to the queue.
  6. 0:14 Build now opens a pull request that carries the brief, not the code, with auto-merge off.
  7. 0:23 Nothing builds until a person promotes it.
  8. 0:25 The guide covers the rest.

Synthetic example. Read the guide

Name the machine, not the average

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 One machine in the fleet is climbing.
  2. 0:02 The team view shows an average.
  3. 0:06 Group every finding by the install that fired it.
  4. 0:09 Keep the numbers with it.
  5. 0:13 Each card names the root cause, the measured samples, and the suggested fix.
  6. 0:18 An applied fix shows before and after.
  7. 0:23 Unmeasured is said plainly, never scored a win.
  8. 0:26 The guide has the caps.

Synthetic example. Read the guide

Requested is not contained

Read the guide. Product version RepoOps main at 509e8e8ad (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A score says little. Which asset, which rule, which session?
  2. 0:06 A code defect, a runtime AI attack and a toolchain attack stay separate.
  3. 0:11 Each names its detector.
  4. 0:13 The case lists the affected assets and the exploit evidence.
  5. 0:17 What no detector reads is named, not counted as clean.
  6. 0:23 An owner approves containment for this repository.
  7. 0:26 Until the desktop confirms it, it reads pending.

Synthetic example. Read the guide

A blank is not a pass

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Your loops run overnight, unattended.
  2. 0:03 Nobody has priced what that costs.
  3. 0:06 RepoOps runs four checks over data it already holds.
  4. 0:09 No signal reads unknown, never green.
  5. 0:13 Gate coverage on agent pull requests, skill provenance, secrets in logs, rules past re-audit.
  6. 0:23 Read the unknowns first.
  7. 0:25 The team page carries counts, never a secret.

Synthetic example. Read the guide

The handoff the next session reads

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Tomorrow you reopen the repo.
  2. 0:02 Nothing says where last night stopped.
  3. 0:06 The captured facts are not the account.
  4. 0:08 Only the person who was there writes why.
  5. 0:13 The hook scaffolds three sections and rolls up the session's turns.
  6. 0:17 A drafted entry waits in a sidecar until you confirm it.
  7. 0:23 The next session opens with what got built and what is next.

Synthetic example. Read the guide

Set the boundary before the connection

Read the guide. Product version RepoOps main at 93f5ec71b (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A setup screen can turn into accidental sharing with one careless connection.
  2. 0:06 Decide what may leave first, then connect repositories, keys, and the team.
  3. 0:13 RepoOps shows the effective mode, the redacted preview and the masked key status.
  4. 0:18 Then team consent, daemon state and the publishing rows.
  5. 0:23 Wire only what the work needs, then verify every resulting reported state.

Synthetic example. Read the guide

The URL is the credential

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A dashboard screenshot goes stale quickly. A broad login grants too much.
  2. 0:06 A share link is a credential, not a screenshot or a seat.
  3. 0:13 It binds one live view, an optional repository and an expiry.
  4. 0:17 Every open checks the personal-repository deny-list first.
  5. 0:23 Share the narrowest link, then revoke it promptly when the question ends.

Synthetic example. Read the guide

Read the checkout before the host does

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 You are about to deploy.
  2. 0:01 Nobody has read the tree yet.
  3. 0:06 RepoOps reads the checkout before the host.
  4. 0:09 Four checks, one verdict, and nothing is executed.
  5. 0:13 A variable the code reads and nothing declares.
  6. 0:16 The verdict is blocked, and the card names the exact fix.
  7. 0:23 Declare it, re-run, ready to ship.
  8. 0:26 The same check can gate a push.

Synthetic example. Read the guide

Count what arrived, not what connected

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 You pointed a gateway at the local receiver.
  2. 0:02 Nothing shows up yet.
  3. 0:06 A span is kept only when it describes a model call.
  4. 0:09 HTTP traces are dropped.
  5. 0:13 The tab says which: spans with no AI calls, or nothing.
  6. 0:17 The preview shows what would leave; prompts never ride a span.
  7. 0:23 Export when the preview reads right.
  8. 0:25 The ledger keeps each receipt, stats only.

Synthetic example. Read the guide

The bill is not the lever

Read the guide. Product version RepoOps main at 7aab4cd82 (after v0.3.2); rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The bill went up.
  2. 0:01 The bill does not say which lever moved.
  3. 0:06 Six levers set the cost.
  4. 0:08 RepoOps grades each one from telemetry you already hold.
  5. 0:13 A lever with no signal reads a dash, never a low grade.
  6. 0:17 The priced fix names the surface and opens its pull request.
  7. 0:23 Change one lever.
  8. 0:24 The saving is measured after the change lands.

Synthetic example. Read the guide

Identity proof is not team membership

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A valid identity provider response should never create access to the wrong team.
  2. 0:06 Authentication proves an identity. Membership still decides whether that identity belongs here.
  3. 0:13 RepoOps verifies the response, blocks replay and rechecks the Enterprise tier.
  4. 0:18 Then it requires an existing team membership.
  5. 0:23 Test one member, one non-member, and the audit trail before rollout.

Synthetic example. Read the guide

Treat traffic as a question

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-27.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Repeated navigation can masquerade as adoption when reloads and curiosity count alike.
  2. 0:06 Treat visits as a menu signal, never as proof of value or satisfaction.
  3. 0:13 RepoOps counts hosted page visits for thirty days, grouped by tab.
  4. 0:17 It keeps no user identity and shows the last visit date.
  5. 0:23 Use the ranking to investigate placement, then validate why people opened each surface.

Synthetic example. Read the guide

Proof that a lesson did something

Read the guide. Product version RepoOps main at 93f5ec71b (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Your team wrote the lesson down.
  2. 0:02 Nobody knows if it reached anyone.
  3. 0:06 A saved lesson is not prevention.
  4. 0:08 RepoOps counts what was delivered, and what ran.
  5. 0:13 The lens shows delivered, caught, missed, and did not run.
  6. 0:16 A guard behind a disabled hook is not a clean run.
  7. 0:23 Read the receipts, not the count.
  8. 0:25 Sharing stays off until you allow it.

Synthetic example. Read the guide

What the AI bill was actually made of

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 The monthly bill is one number.
  2. 0:02 It does not say which repository.
  3. 0:06 RepoOps sums every captured turn per repository.
  4. 0:09 The rate card prices it at read time.
  5. 0:13 Thirty days of events, tokens, cache and cost.
  6. 0:16 Per repository, then per day.
  7. 0:19 A model the card cannot price counts zero.
  8. 0:23 Read what was captured before judging the total.
  9. 0:26 The guide names the limits.

Synthetic example. Read the guide

Start with the case that needs you

Read the guide. Product version RepoOps main at 509e8e8ad (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 Start with the case that needs you: overdue first, then by severity.
  2. 0:06 Set repository, environment, service and time once.
  3. 0:10 The page says how old its read is.
  4. 0:13 A class nothing observes reads no source, never zero.
  5. 0:17 Open the case, and Evidence coverage shows what is missing.
  6. 0:23 A built fix still waits for your decision.
  7. 0:25 A failing source is named, not hidden.

Synthetic example. Read the guide

A record anyone can check

Read the guide. Product version RepoOps v0.3.1; rendered 2026-09-16.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 A merged change claims an author.
  2. 0:02 Nobody has checked the claim.
  3. 0:06 RepoOps recomputes the digest and checks the signature.
  4. 0:09 Tampering fails honestly.
  5. 0:13 A valid signature is not a signer you know.
  6. 0:16 Pin the key, or find the digest in the witnessed log.
  7. 0:23 Hand over the record.
  8. 0:24 An offline check reaches the same verdict, no server needed.

Synthetic example. Read the guide

A code map that shows its sources

Read the guide. Product version RepoOps main at b0bb02812 (after v0.3.2); rendered 2026-09-26.

30.1 s, captions on. Narration: Microsoft Zira Desktop (provisional voice; an approved narration source is pending).Transcript
Read the narration
  1. 0:00 New teammates ask how the repository works, but the source keeps changing.
  2. 0:06 Generate a small wiki from the code, and make each claim point back to evidence.
  3. 0:13 Beside the generated text, RepoOps shows citation status and claim receipts.
  4. 0:18 Lessons and decisions that touch the same files sit alongside.
  5. 0:23 Read the map, then follow its citations before trusting the summary.

Synthetic example. Read the guide

Coverage

The denominator is the canonical feature registry: every leaf in the product navigation outside the reference drawer, counted once per guide route. The public route manifest states that count and the number of stories published against it, so coverage is a fraction with a fixed bottom rather than a percentage over whatever has shipped. A feature without a story here has an open row on the ledger, not a placeholder player.

Last updated