EvidenceContext

Standards define observable conditions. Their applicability is specified by phase, role and action, and their effect follows a Compulsory, Conditional or Advised classification.

Reference

B1

Evidence type

Design specification

Source reference

Standards Taxonomy & Pattern Intelligence Loop v2.1 §§3.1–3.6, 5.2–5.3; Controlled Facts Register v2.8, CF-STD-008/011/013.

Source date

Taxonomy: 4 August 2026. Register: 14 August 2026.

Source basis

Company-authored specification supports the stated design.

Implementation status

Documented operating design. Component availability and execution evidence follow the published build record.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Standards

Sources: Standards Taxonomy & Pattern Intelligence Loop v2.1 · 4 August 2026; Controlled Facts Register v2.8 · 14 August 2026.

The Launch OS design connects applicable conditions to progression checks and evidence records. The documented evidence requirements for each condition determine what can be reviewed. Advised conditions remain visible while participation continues.

Reference

B2

Evidence type

Design specification

Source reference

Standards Taxonomy & Pattern Intelligence Loop v2.1 §§3.3, 5.2–5.3; Launch OS Architecture v2.0 §§3.4, 4.12–4.13; Controlled Facts Register v2.8, CF-STD-008/011/013.

Source date

Taxonomy: 4 August 2026. Launch OS: 30 July 2026. Register: 14 August 2026.

Source basis

Governing taxonomy and controlled-fact rules qualify the progression design.

Implementation status

Documented operating design. Component availability and execution evidence follow the published build record.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Standards

Sources: Standards Taxonomy & Pattern Intelligence Loop v2.1 · 4 August 2026; Launch OS Architecture v2.0 · 30 July 2026; Controlled Facts Register v2.8 · 14 August 2026.

Readiness views are designed to show applicable conditions and evidence states by enforcement class, with links to supporting records. Reviewers use that context in their own diligence and decisions.

Reference

B3

Evidence type

Design specification

Source reference

Master Canon v3.9 §8.2; Standards Taxonomy & Pattern Intelligence Loop v2.1 §§8.7–8.9.

Source date

Canon: 31 August 2026. Taxonomy: 4 August 2026.

Source basis

The governing rule specifies readiness counts by enforcement class.

Implementation status

Documented operating design. Component availability and execution evidence follow the published build record.

Artifact access

The taxonomy is marked for data-room access under NDA. The underlying canon is not published in this index; its release scope requires confirmation.

Owning function

Product

Sources: Master Canon v3.9 · 31 August 2026; Standards Taxonomy & Pattern Intelligence Loop v2.1 · 4 August 2026.

The Pattern Intelligence Loop provides a human-led process for examining recurring failure modes and proposing updates to standards. Changes follow documented review, version control and applicability decisions.

Reference

B4

Evidence type

Design specification

Source reference

Standards Taxonomy & Pattern Intelligence Loop v2.1 §§9.1–9.2, 9.5, 9.9, 10.6–10.7.

Source date

4 August 2026.

Source basis

Company-authored specification supports the stated design.

Implementation status

Documented review and change process. Completed review cycles require their own decision records.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Standards

Sources: Standards Taxonomy & Pattern Intelligence Loop v2.1 · 4 August 2026.

The evidence architecture links venture work to attributed records that can support permissioned review across work surfaces. Artifact references, validation state and access rules travel with the record.

Reference

C1

Evidence type

Design specification

Source reference

Technical Architecture v2.0 §§11.4, 19.2–19.4.

Source date

30 July 2026.

Source basis

Company-authored specification supports the stated design.

Implementation status

Documented operating design. Component availability and execution evidence follow the published build record.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Brand / Strategy

Sources: Technical Architecture v2.0 · 30 July 2026.

The Evidence Model specifies source references, provenance, validation state and version lineage. These fields let a reviewer inspect what changed and the basis of the recorded state.

Reference

C2

Evidence type

Design specification

Source reference

Technical Architecture v2.0 §§11.4, 19.2, 19.5.

Source date

30 July 2026.

Source basis

Company-authored specification supports the stated design.

Implementation status

Documented evidence schema and retention model. Stored records and version histories establish implementation for a particular scope.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Product

Sources: Technical Architecture v2.0 · 30 July 2026.

Launch OS structures lifecycle work; the Evidence Model preserves its records and review context; the Alpha AI Engine is designed to produce source-linked interpretation from validated, permissioned evidence.

Reference

C3

Evidence type

Design specification

Source reference

Launch OS Architecture v2.0 §§3.3–3.5; Technical Architecture v2.0 §§11.4, 19.2–19.4; Alpha AI Engine v2.1 §§4–5.

Source date

Launch OS and Technical Architecture: 30 July 2026. AI Engine: June 2026; day not stated.

Source basis

Company-authored specification supports the stated design.

Implementation status

Connected architecture described for active build. End-to-end availability requires the corresponding release evidence.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Product

Sources: Launch OS Architecture v2.0 · 30 July 2026; Technical Architecture v2.0 · 30 July 2026; Alpha AI Engine v2.1.

The architecture defines role and permission controls for access to evidence artifacts. A reviewer’s authorized scope determines which records and context can be disclosed.

Reference

D1

Evidence type

Design specification

Source reference

Technical Architecture v2.0 §19.4, Permission & Access Model.

Source date

30 July 2026.

Source basis

Company-authored specification supports the stated design.

Implementation status

Documented access-control model. Operational permissions require environment-specific configuration and test records.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Product

Sources: Technical Architecture v2.0 · 30 July 2026.

The evidence architecture includes attributed decision records, timestamps and version lineage. These records are intended to preserve questions, review outcomes and rationale for subsequent diligence.

Reference

D2

Evidence type

Design specification

Source reference

Technical Architecture v2.0 §§19.2–19.3, Evidence Object Schema and Evidence Graph Structure.

Source date

30 July 2026.

Source basis

Company-authored specification supports the stated design.

Implementation status

Documented decision-record structure. Attributed decision artifacts establish its use for a particular review.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Product

Sources: Technical Architecture v2.0 · 30 July 2026.

The Launch OS design continues into post-launch stewardship through reporting, material-change records, monitoring and remediation workflows. The relevant participation context determines the work and records required.

Reference

D3

Evidence type

Design specification

Source reference

Launch OS Architecture v2.0 §§4.11–4.13, Post-Launch Stewardship, Remediation and Decision Logging.

Source date

30 July 2026.

Source basis

Company-authored specification supports the stated design.

Implementation status

Documented stewardship workflow. Operational reports, monitoring and remediation records establish its use.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Product

Sources: Launch OS Architecture v2.0 · 30 July 2026.

The operating model requires material changes to record their rationale, owner, affected scope and review outcome. Version history preserves the relationship between an updated requirement and the records that rely on it.

Reference

D4

Evidence type

Design specification

Source reference

Master Canon v3.9 §11.1; Technical Architecture v2.0 §10.6, Governed Change Control.

Source date

Canon: 31 August 2026. Technical Architecture: 30 July 2026.

Source basis

Governing change rules and architecture define the required record.

Implementation status

Documented change process. Each completed change requires its own approval, version and change-log record.

Artifact access

Technical Architecture is marked for data-room access under NDA. The canon is not published in this index; its release scope requires confirmation.

Owning function

Governance

Sources: Master Canon v3.9 · 31 August 2026; Technical Architecture v2.0 · 30 July 2026.

The Alpha AI Engine is specified as a governed retrieval architecture. It assembles relevant, permissioned evidence and uses that context to support traceable interpretation for the user’s task.

Reference

E1

Evidence type

Design specification

Source reference

Alpha AI Engine v2.1 §§4–5, Evidence Graph and retrieval architecture.

Source date

June 2026; day not stated.

Source basis

Company-authored specification supports the stated design.

Implementation status

The cited source describes active build and a pre-launch architecture. Live capability requires release and execution evidence.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Product / AI

Sources: Alpha AI Engine v2.1.

The platform’s intelligence is intended to support a stakeholder’s own diligence and decisions. The registered advice and regulated-role disclosures define the boundaries that apply to its use.

Reference

E2

Evidence type

Governed boundary

Source reference

Registered Disclosures v3.1.0, DISC-ADVICE-01 and DISC-FOOT-01; Registered Wording v3.1.0, LW-010 and LW-011, within Editorial System v3.2.

Source date

Disclosures: 18 August 2026. Wording: 14 August 2026.

Source basis

Registered company wording defines the communication boundary.

Implementation status

A governing communication boundary. Product implementation is a separate question.

Artifact access

Applicable disclosure text is published on Claims & Disclosures. The underlying registry files are not published in this index.

Owning function

Legal & Regulatory

Sources: Registered Disclosures · Editorial System v3.2; Registered Wording · Editorial System v3.2.

Compliance Intelligence is designed to organize regulatory-source references and their effective context for review. Source provenance, jurisdiction and date are part of the proposed information model.

Reference

E3

Evidence type

Design specification

Source reference

Regulatory Risk & Compliance System v1.1 §§2 (P1, P2, P6, P8), 6.1–6.2; Technical Architecture v2.0 §§11.4, 19.2.

Source date

Compliance System: 22 August 2026. Technical Architecture: 30 July 2026.

Source basis

The compliance method is ratified in its stated scope; register schemas are provisionally adopted.

Implementation status

Documented method and information model. Populated registers and operational outputs require their own evidence.

Artifact access

Compliance System is marked internal. Technical Architecture is marked for data-room access under NDA. Source release follows the applicable access process.

Owning function

Compliance

Sources: Regulatory Risk & Compliance System v1.1 · 22 August 2026; Technical Architecture v2.0 · 30 July 2026.

The Alpha AI Engine design links retrieved context and generated outputs to source records, versions and access scope. Reviewers can use those references to examine the basis of an interpretation.

Reference

E4

Evidence type

Design specification

Source reference

Alpha AI Engine v2.1 §§4–5 and §10, Governance & the learning loop.

Source date

June 2026; day not stated.

Source basis

Company-authored specification supports the stated design.

Implementation status

Documented output traceability. Particular generated outputs require their own source, version and access records.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Product / AI

Sources: Alpha AI Engine v2.1.

The AI specification includes evaluations for correctness, safety, information leakage and policy adherence. Permission checks, version records and controlled changes are part of that design.

Reference

E5

Evidence type

Design specification

Source reference

Alpha AI Engine v2.1 §5, evaluation stage and engineering properties; §10, governance and logged changes.

Source date

June 2026; day not stated.

Source basis

The cited source describes evaluation, permissions and governance. Detailed test dimensions require their own specification.

Implementation status

Documented evaluation controls. Completed evaluations require scoped test results and their dates.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Product / AI

Sources: Alpha AI Engine v2.1.

ALPHA supports access, settlement and incentives within the ecosystem. The adopted omnichain architecture uses LayerZero V2 OFT transport with source-chain burning and destination-chain minting under configured route controls.

Reference

F1

Evidence type

Design specification

Source reference

AlphaTokenOFT.sol: OFT inheritance, _debit and _credit; deployment registry v2.0.0: environments; Master Canon v3.9 §3.1.

Source date

Contract source: version/date not declared. Registry last updated: 8 May 2026. Canon: 31 August 2026.

Source basis

Implementation source supports the transport mechanism; the canon describes ALPHA’s ecosystem functions.

Implementation status

Code and configuration are available in the source estate. Operational chain and route state requires deployment and verification records.

Artifact access

The source artifact is not published in this index. Its release and access scope require confirmation through the access process.

Owning function

Protocol Eng

Sources: AlphaTokenOFT implementation; Omnichain deployment configuration; Master Canon v3.9 · 31 August 2026.

The incentives design connects eligibility and release conditions to program rules and recorded participation. Credit balances and their permitted uses follow the governing rules of each program.

Reference

F2

Evidence type

Design specification

Source reference

Launch OS Architecture v2.0 §§8.6–8.7, Incentive Eligibility and Evidence Linkage; Master Canon v3.9 §3.1.

Source date

Launch OS: 30 July 2026. Canon: 31 August 2026.

Source basis

Named sources describe program conditions and evidence linkage. Each program’s rules determine its permitted uses.

Implementation status

Documented participation design. Issuance, recognition and permitted use require the relevant program record.

Artifact access

Launch OS is marked for data-room access under NDA. Program-specific rules and records follow their applicable access process.

Owning function

Programs

Sources: Launch OS Architecture v2.0 · 30 July 2026; Master Canon v3.9 · 31 August 2026.

Equity participation and ALPHA participation have separate terms. ALPHA’s ecosystem functions and any offering conditions are described through the applicable governing documentation and registered disclosures.

Reference

F3

Evidence type

Design specification

Source reference

Master Canon v3.9 §3.1; Registered Disclosures v3.1.0, DISC-FOOT-01, DISC-OFFER-01 and DISC-ELIG-01.

Source date

Canon: 31 August 2026. Disclosures: 18 August 2026.

Source basis

The cited sources document ALPHA and offering boundaries. Equity participation requires its own governing instrument.

Implementation status

Participation terms are governed by the relevant documents. Each offering and participant requires its applicable record.

Artifact access

Registered disclosures are public. Offering and equity documents follow their applicable access and eligibility process.

Owning function

Legal & Regulatory

Sources: Master Canon v3.9 · 31 August 2026; Registered Disclosures · Editorial System v3.2.

The security architecture specifies identity and access controls, protected administrative actions, route controls and incident response responsibilities. Evidence of implementation and testing must be scoped to the particular component and environment.

Reference

G1

Evidence type

Design specification

Source reference

Security & Assurance Strategy v2.1 §§6–10, access, key management, audit readiness, monitoring and incident response; Technical Architecture v2.0 §§19.4, 20.2–20.4.

Source date

Security Strategy: 16 June 2026. Technical Architecture: 30 July 2026.

Source basis

Company-authored security design; the Security Strategy body carries “Draft — source pending review.”

Implementation status

Controls are described in their stated design scope. Component implementation and testing require environment-specific evidence.

Artifact access

Named design documents are marked for investor data-room access under NDA. This page publishes an explanation; source access follows the applicable process.

Owning function

Security

Sources: Security & Assurance Strategy v2.1 · 16 June 2026; Technical Architecture v2.0 · 30 July 2026.

The security strategy describes a planned independent smart-contract audit before public launch. An audit report, its scope and its date are the evidence needed to substantiate an audit-completion statement.

This material may contain forward-looking statements and illustrative examples subject to risks, uncertainties, and change, including through governance decisions, regulatory developments, and technical constraints. Go-live timing is a planning reference, not a commitment.

Reference

G2

Evidence type

Documented plan

Source reference

Security & Assurance Strategy v2.1 §8, Smart-contract audit readiness and the mainnet gate.

Source date

16 June 2026.

Source basis

Company-authored audit plan; the source body carries “Draft — source pending review.”

Implementation status

Documented plan. Audit engagement, completion and remediation require their own dated records.

Artifact access

The strategy is marked for data-room access under NDA. This index provides no completed independent-audit report.

Owning function

Security

Sources: Security & Assurance Strategy v2.1 · 16 June 2026.

The OFT implementation contains configured peer routes, pause controls and transfer limits. Deployment records and tests for each chain and route are needed to establish its operational state.

Reference

G3

Evidence type

Implementation source

Source reference

AlphaTokenOFT.sol: pause/unpause, setOutboundRateLimit, setInboundRateLimit, _debit and _credit; deployment registry v2.0.0: environments.

Source date

Contract source: version/date not declared. Registry last updated: 8 May 2026.

Source basis

Implementation source contains the named controls.

Implementation status

Source code and configuration. Deployed controls and configured limits require chain-specific execution evidence.

Artifact access

The source artifact is not published in this index. Its release and access scope require confirmation through the access process.

Owning function

Protocol Eng

Sources: AlphaTokenOFT implementation; Omnichain deployment configuration.

Becoming Alpha, Inc. is a Delaware Public Benefit Corporation. Its company record is the reference for that corporate identity.

Reference

H1

Evidence type

Company description

Source reference

Master Canon v3.9 §1.1, company identity.

Source date

31 August 2026.

Source basis

Company-reported legal identity.

Implementation status

Company description. External confirmation requires the relevant corporate record.

Artifact access

The public company explanation is linked below. A corporate filing artifact is not published in this index.

Owning function

Corporate / Legal & Regulatory

Sources: Master Canon v3.9 · 31 August 2026.

The Company section identifies the Becoming Alpha executive team and their responsibilities. Its named profiles are the current public reference for this company-reported information.

Reference

H2

Evidence type

Company description

Source reference

Master Canon v3.9 §9.2, operating context; public Company / Team profiles.

Source date

Canon: 31 August 2026. The public profile page states no source publication date.

Source basis

Company-reported profiles. The canon describes operating roles; named profiles are maintained on the public Team page.

Implementation status

Published company profiles. Appointment verification requires the relevant company records.

Artifact access

Named profiles are public. Supporting appointment records are not published in this index.

Owning function

People

Sources: Master Canon v3.9 · 31 August 2026.