KANE/MISSION CONTROL

Now · recap

Official time

9:54 PMPDT

Submissions due

Locked

Next on the agenda

—

06 / Recap

That's a wrap.

Reviewed aggregates from the day, and every published ship page to share.

The day, verified

Panel 1 of 2

Registered69
Checked in0
Passports active48
Active teams44
Teams with proof18
Kane executions138
Builds validated0
Suspected detections25
Bugs confirmed4
Fixed + reverified3
Evidence packs1
Help requests open14
Median wait for a mentor—
Submissions finalized11
Photos published0
Ship pages live12

11of 44

Submissions finalized · ✓ Verified

Kane executions

How it’s counted

Kane executions

Counts: Distinct (source, execution id) Kane runs with a terminal event, split by status
Per / out of: Execution (not a build, not a release)
Source: kanehack CLI / MCP / CI adapters
Trust gate: Source-verified run with a terminal exit

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

138

Completed runs · every outcome96 passed · 40 failed · 1 errored/blocked

Builds validated

How it’s counted

Builds validated

Counts: Distinct repository + commit SHA pairs with a verified passing Kane run
Per / out of: Project commit (counted once, however many runs)
Source: GitHub repository link + Kane run
Trust gate: Provenance links the run to the exact SHA

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

Evidence-linked commits

Bugs confirmed

How it’s counted

Bugs confirmed

Counts: Distinct human-confirmed product defects with attributable Kane evidence
Per / out of: Confirmed issue (infra/auth-only errors excluded)
Source: Defects + Kane evidence
Trust gate: Confirming actor + evidence

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

Reviewed, reproducible defects

Verified

Fixed + reverified

How it’s counted

Fixed + reverified

Counts: Confirmed defects with a later passing Kane run on a different (corrected) commit
Per / out of: Confirmed defect
Source: Defects + verification runs + SHA
Trust gate: Verified before/after runs on distinct revisions

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

Closed feedback loops

Verified

Photos published

How it’s counted

Photos published

Counts: Distinct published event photos
Per / out of: Photo
Source: Media DB
Trust gate: Per-person consent + staff approval

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

Approved with consent

Mission Control · connecting…

KANE/MISSION CONTROL

Now · recap

Official time

9:54 PMPDT

Submissions due

Locked

Next on the agenda

—

06 / Recap

That's a wrap.

Reviewed aggregates from the day, and every published ship page to share.

The day, verified

Panel 1 of 2

Registered69
Checked in0
Passports active48
Active teams44
Teams with proof18
Kane executions138
Builds validated0
Suspected detections25
Bugs confirmed4
Fixed + reverified3
Evidence packs1
Help requests open14
Median wait for a mentor—
Submissions finalized11
Photos published0
Ship pages live12

11of 44

Submissions finalized · ✓ Verified

Kane executions

How it’s counted

Kane executions

Counts: Distinct (source, execution id) Kane runs with a terminal event, split by status
Per / out of: Execution (not a build, not a release)
Source: kanehack CLI / MCP / CI adapters
Trust gate: Source-verified run with a terminal exit

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

138

Completed runs · every outcome96 passed · 40 failed · 1 errored/blocked

Builds validated

How it’s counted

Builds validated

Counts: Distinct repository + commit SHA pairs with a verified passing Kane run
Per / out of: Project commit (counted once, however many runs)
Source: GitHub repository link + Kane run
Trust gate: Provenance links the run to the exact SHA

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

Evidence-linked commits

Bugs confirmed

How it’s counted

Bugs confirmed

Counts: Distinct human-confirmed product defects with attributable Kane evidence
Per / out of: Confirmed issue (infra/auth-only errors excluded)
Source: Defects + Kane evidence
Trust gate: Confirming actor + evidence

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

Reviewed, reproducible defects

Verified

Fixed + reverified

How it’s counted

Fixed + reverified

Counts: Confirmed defects with a later passing Kane run on a different (corrected) commit
Per / out of: Confirmed defect
Source: Defects + verification runs + SHA
Trust gate: Verified before/after runs on distinct revisions

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

Closed feedback loops

Verified

Photos published

How it’s counted

Photos published

Counts: Distinct published event photos
Per / out of: Photo
Source: Media DB
Trust gate: Per-person consent + staff approval

A dash (—) means unknown, never zero. Signals are never added into one score or compared across projects.

Approved with consent

That's a wrap.

↗ The day, verified

Kane executions

Builds validated

Bugs confirmed

Fixed + reverified

Photos published

That's a wrap.

↗ The day, verified

Kane executions

Builds validated

Bugs confirmed

Fixed + reverified

Photos published

The day, verified

The day, verified