The Labs Lifecycle

Every prototype follows a transparent, governed path. Nothing graduates without community validation.

Stage 1
Submitted

Builder opens a prototype submission via the submissions repo. Labs team scores it against the 5-dimension rubric.

Stage 2
Active — Experimental

Scoring ≥ 10/15 — prototype goes live for community testing. Open for feedback, bugs, and iteration.

Stage 3
Under Review

Builder submits a graduation request. CPO + CISO conduct a final review including security assessment.

Stage 4
Graduated

Approved — code migrated to Autheo core. Proof of graduation recorded on-chain.

Stage 5
Archived

Discontinued or superseded. Repo preserved for reference.

Qualification Criteria

Submissions are scored across five dimensions by the Labs team. A minimum of 10/15 is required to enter Active–Experimental status.

Qualification Rubric

Innovation Value

Does the prototype address a genuine gap or advance Autheo's quantum-native vision?

Hypothesis Clarity

Is the experiment well-defined with measurable success criteria and a clear README?

Isolation Integrity

Is the prototype fully isolated from Autheo mainnet with no shared state or risk bleed?

Risk Transparency

Are all known risks disclosed — security, performance, stability — with appropriate warnings?

Roadmap Alignment

Does the prototype align with Autheo's strategic priorities and quantum-native roadmap?

Minimum passing score10 / 15

Automatic Disqualifiers

Any of the following will result in immediate rejection, regardless of rubric score:

  • Any dependency on Autheo mainnet state
  • Missing or incomplete README documentation
  • No risk disclosure provided
  • Rubric score below 10/15
  • Unresolved P0/P1 bugs at review time
  • Prototype not fully isolated to testnet
  • Undisclosed third-party code dependencies

Community Testing

Active prototypes are tested by the Autheo community. Feedback is structured, prioritized, and tracked publicly.

GitHub Issues

All bugs and feedback are filed as GitHub Issues on the prototype repo. P0–P3 severity labels keep triage structured.

Discord #labs-feedback

Async community discussion in the dedicated Labs feedback channel. Builder teams monitor daily.

CISO Risk Tracking

Security findings are routed directly to the Autheo CISO. P0 security bugs trigger an immediate prototype pause.

PriorityDescriptionResponse SLA
P0CriticalPrototype unusable24 hours — pause triggered
P1MajorSignificant functionality broken72 hours
P2MinorWorkaround exists2 weeks
P3EnhancementNice-to-have improvementBest effort

Graduation Pathway

Qualifying for graduation means your experiment has proven its value and safety. Here's the six-step process.

01

Submit Graduation Request

Builder opens a formal request in the submissions repo with evidence of community testing completion.

02

Qualify Testing Threshold

Minimum 60 days active, measurable test coverage, and all P0/P1 bugs resolved.

03

CISO Security Review

The Autheo CISO conducts a full security assessment. No critical findings allowed.

04

CPO + CISO Decision

Joint approval required from both the CPO and CISO. Decision is documented publicly.

05

Handover Package

Builder delivers a complete handover: audit report, deployment guide, operational runbook.

06

Mainnet Deployment

Code is migrated to Autheo core org. On-chain graduation proof is recorded.

Graduation decisions require joint approval from the Autheo CPO and CISO. Decisions are documented publicly.

After Labs

What happens when a prototype graduates — or doesn't.

Graduated

Code is migrated to the Autheo core organization. A graduation proof is recorded on-chain. The Labs repo is archived for reference. Builder credit is preserved.

Archived

Prototypes that are discontinued, superseded, or fail CISO review are archived. Repos remain public for learning. Builders may resubmit improved versions.