Repository guide · 0 diagrams

View source on GitHub ↗
Original documentation, preserved from the repository. Historical projections and scenario ambitions are not evidence of live performance. See the current readiness record for deployment requirements.

α-AGI MARK Demo Runbook

This runbook describes the local α-AGI MARK financing-market demonstration. Begin with the quick start or browser capital-to-work lab. Local test accounts and reports are not an independently commissioned production deployment. See computer-work handoff for actual worker admission and acceptance.

Prerequisites

Execution Steps

  1. Launch the demo

    npm run demo:alpha-agi-mark

    The orchestrator automatically:

    • boots a Hardhat chain
    • deploys the NovaSeedNFT, AlphaMarkRiskOracle, AlphaMarkEToken, and AlphaSovereignVault contracts
    • performs investor buys and validator approvals
    • pauses and resumes trading to verify safety controls
    • demonstrates pre-launch base asset retargeting (ETH -> ERC-20 stablecoin)
    • proves the sovereign vault pause/unpause circuit breaker
    • finalizes the launch with ignition metadata and prints a comprehensive recap
    • emits an owner parameter matrix table in the console and inside the recap dossier
      • runs the triple-verification matrix to confirm supply, pricing, capital flows, and participant ledgers agree across all independent checks

    Need everything in one keystroke? Run npm run demo:alpha-agi-mark:full to execute the demo, replay the verification, emit the owner matrix, synthesise the integrity dossier, and forge the risk lattice without running additional commands.

  2. Inspect recap artifacts

    At the end of the run the script emits a JSON recap under demo/alpha-agi-mark/reports/alpha-mark-recap.json and a cinematic HTML dashboard at demo/alpha-agi-mark/reports/alpha-mark-dashboard.html. The recap dossier contains:

    • contract addresses
    • owner governance parameters
    • consolidated ownerControls snapshot of every pause/whitelist/override lever
    • validator council roster and votes
    • bonding curve statistics (supply, reserve balance, pricing)
    • launch outcome summary, including sovereign vault manifest, acknowledgement metadata, and treasury balance
    • breakdown of native vs. external sovereign intake plus the ignition-mode badge captured in the recap
    • ownerParameterMatrix providing a full owner control matrix with descriptions
    • cross-reference visuals from the Operator Empowerment Atlas and Operator Command Console for stakeholder briefings
    • verification snapshot documenting the triple-check consensus across supply, pricing, capital flows, and contribution tallies
  3. Brief stakeholders with the interactive operator console

    npm run console:alpha-agi-mark

    The console presents an interactive menu with mission summary, owner control deck, participant ledger, validator council tallies, the triple-verification matrix, timeline excerpts, and a dynamically generated Mermaid systems diagram. Use --snapshot in automation to produce a one-shot textual briefing.

  4. Render the owner control matrix at any time

    npm run owner:alpha-agi-mark

    The command reads the latest recap dossier and prints a tabular summary of every operator control lever.

  5. Render (or re-render) the sovereign dashboard

    npm run dashboard:alpha-agi-mark

    This regenerates the HTML dossier using the latest recap JSON, useful after manual parameter tweaks.

  6. Run the offline triangulation verifier

    npm run verify:alpha-agi-mark

    The script replays the trade ledger from the recap, recomputes the bonding-curve math independently, and prints an arithmetic consistency table. All checks must pass; even 100% does not establish provider provenance, buyer acceptance, an independent audit or production readiness. The recap now carries a verification.summary payload (confidence index, passed/total counts, verdict, labelled checks) so the console and dashboard retain the same four-check historical summary. Offline verification adds checks and reports its own denominator; neither score is a probability of correctness.

  7. Layer in stochastic assurance

    npm run verify:alpha-agi-mark:stochastic

    Generates alpha-mark-stochastic-proof.json plus a mermaid-enhanced Markdown brief that logs ledger replay parity and 250 Monte Carlo stress runs. The dossier highlights reserve solvency, supply bounds, and pricing monotonicity so a non-technical steward can cite two independent verification stacks in executive briefings.

  8. Emit the integrity dossier for stakeholder sign-off

    npm run integrity:alpha-agi-mark

    Produces demo/alpha-agi-mark/reports/alpha-mark-integrity.md, a Markdown control-room report with the verification table, owner command deck snapshot, and a mermaid contribution pie chart. Circulate it alongside the dashboard for executive approval.

  9. Forge the empowerment pulse dossier

    npm run pulse:alpha-agi-mark

    Generates demo/alpha-agi-mark/reports/alpha-mark-empowerment.md, merging a quadrant chart, capital pie, and timeline into a single empowerment brief. It summarizes the local recap, validator quorum and owner controls. Any multiplier is a descriptive demo metric, not measured labor productivity or a financial return.

  10. Synthesize the risk lattice dossier

npm run lattice:alpha-agi-mark

Generates demo/alpha-agi-mark/reports/alpha-mark-risk-lattice.md, which layers a mermaid mindmap and flowchart over the control deck, verification verdict, reserve telemetry, and (when available) the empowerment multiplier. Hand this to executives who need a single-page risk and assurance blueprint.

  1. Publish the cinematic mission timeline
npm run timeline:alpha-agi-mark

Creates demo/alpha-agi-mark/reports/alpha-mark-timeline.md, blending a Mermaid timeline with a tabular ledger of every orchestrated action. Ideal for board briefings or audit evidence packs.

  1. Run unit tests before review
npx hardhat test --config demo/alpha-agi-mark/hardhat.config.ts

The AlphaMarkOwnerControls.test.ts suite walks every governance actuator (curve tuning, whitelist, oracle override, pause/emergency exit, abort, and residual withdrawal) so board operators can demonstrate contractual control with a single automated report.

  1. Advanced: explicitly authorized external-network execution

This broadcasts real transactions and spends funds; it is not a dry-run or a required quick-start step. Use disposable testnet accounts only after reviewing the contracts, roles, RPC and planned transactions. Supply signing keys through a protected environment; never paste production keys into shell history. Then explicitly choose the network:

export AGIJOBS_DEMO_DRY_RUN=false
export ALPHA_MARK_NETWORK=sepolia
export ALPHA_MARK_CHAIN_ID=11155111
export ALPHA_MARK_RPC_URL=https://...
# Owner, investor and validator keys must already be provisioned securely.
npm run demo:alpha-agi-mark -- --network sepolia

Provide keys for at least three investors and three validators. The selected owner, investor and validator addresses must all be distinct. Before deployment, the script checks these balances:

Role Planned purchase value Minimum balance
Investor A 1.00 ETH + 0.20 ETH temporary overpayment 1.25 ETH
Investor B 1.20 ETH 1.25 ETH
Investor C 2.30 ETH 2.35 ETH
Owner and each validator Gas only 0.05 ETH each

Each minimum includes a 0.05 ETH gas reserve. These are preflight floors, not live fee estimates; review actual network fees and the owner's deployment costs separately. The script prompts for a launch acknowledgement before any mainnet/testnet transactions proceed.

A run on the in-memory hardhat network is always recorded as a local rehearsal, including when AGIJOBS_DEMO_DRY_RUN=false was left in the environment. The scenario uses explicit purchase-cost and redemption-return limits. Address separation is a configuration check; it does not establish independent ownership or review.

Emergency Controls

When AlphaMarkRiskOracle is constructed with threshold 0, its initial nonempty council defaults to a strict majority: floor(validatorCount / 2) + 1. An empty council cannot approve; repopulating it selects the same default. Existing nonzero thresholds remain explicit owner policy as validators are added, and are capped to the remaining count after removals. Review the quorum after every membership change.

These controls are exercised on the local test chain. External use requires independently reviewed configuration and authorization.

← Back to Alpha AGI Mark