AIEP — 10‑Minute Demonstration

Governed reasoning infrastructure · Piea + Emulator + Live Internet Corpus + Power Governance

1. No traditional OSBoots the AIEP reasoning substrate directly.
2. Internet as substrateLive evidence retrieval — no training dataset.
3. Evidence-bound reasoningEvery inference is hash-committed to a source.
4. Governance controls executionRules enforce, degrade, and refuse — always.
5. Identity continuityNodes migrate without losing state or evidence.
01 1 min Architecture

Boot the AIEP Hardware Substrate

AIEP Trusted Node Booting
Node identity established
Governance substrate loaded
Mirror connectivity active
Evidence pipeline ready

This node is not booting Linux or Windows. It boots the AIEP reasoning substrate directly.

Hardware → AIEP Substrate → Reasoning Environment
02 2 min Evidence

Live Internet Evidence Retrieval

Fetch: legislation.gov.uk
Compute ContentHash
  SHA-256: 4f2a1e8c9b0d3f7a...
Commit EvidenceRecord
  source:    legislation.gov.uk
  hash:      4f2a1e8c9b0d3f7a
  timestamp: 2025-01-01T09:00:00Z
  node_sig:  ed25519:7c3b...

The system does not rely on a training dataset. It reasons over live evidence retrieved from the web.

The internet becomes the knowledge substrate.
03 2 min Reasoning

Piea Reasoning Query

Query: What is the statutory definition of a construction
        contract in UK law?

  Retrieve sources          [OK]
  Hash artefacts            [OK]
  Commit evidence           [OK]
  Execute reasoning chain   [OK]
  Produce answer            [OK]

Answer: Under s.104 Housing Grants, Construction and
Regeneration Act 1996, a "construction contract" means
an agreement with a person for...

Citations:
  [1] legislation.gov.uk/ukpga/1996/53  hash:4f2a...
  [2] legislation.gov.uk/uksi/1998/649  hash:8d9b...

Every statement is linked to a verifiable evidence record. No inference is made without a corresponding hash-committed source.

Evidence-bound reasoning.
04 1 min Product

Forecast Application Proof

AIEP Forecast — Contract Analysis
  Clause:   Notice of Delay (cl. 8.3)
  Input:    Letter dated 12 Jan 2025
  Analysis: Notice served within contractual period
            Time-bar provisions satisfied
  Outcome:  VALID

Evidence record: aiep://forecast/ev/2025-01-12/cl8.3

Forecast demonstrates the AIEP protocol operating inside a real commercial SaaS application — every reasoning step is governed and auditable.

Protocol → Real-world SaaS application.
05 2 min Governance

Power Reduction Scenario

Power budget: 100% → 60%
  Mirror refresh rate:   reduced
  Branch exploration:    reduced
  Evidence hashing:      maintained
  Reasoning execution:   maintained
  Governance gates:      maintained

Power budget: 60% → 30%
  Non-essential processes suspended
  Core reasoning active
  Evidence ledger protected

The system degrades capabilities in a governed order but never violates governance rules. Core integrity is always preserved.

Governed resource degradation.
06 1 min Fail-Closed

Governed Refusal

Request: Run arbitration across 500 reasoning branches

  OPERATION SUPPRESSED

  Reason:
    Insufficient admissible compute budget

  NegativeProofRecord issued
    ref:  aiep://governance/npr/2025-01-01/0042
    hash: d3c9f1a2...

Unsafe operations are refused rather than executed incorrectly. The refusal itself is recorded as a verifiable NegativeProofRecord.

Fail-closed reasoning governance.
07 1 min Migration

Node Migration Demonstration

Power budget: 15%

  Node A state sealed
    identity hash: b7e2...
    evidence refs: 1,204 committed
  Migration record issued
  Node B activated
  Substrate restored

  Piea continues operating.
  Identity: PRESERVED
  Evidence: PRESERVED

Identity and evidence continuity are preserved across hardware nodes. The reasoning substrate migrates; no state is lost.

Substrate continuity across hardware nodes.

Key Takeaways

No OS dependency

AIEP nodes boot a governed reasoning substrate — not a general-purpose operating system.

Live evidence, not training data

Every reasoning step is anchored to a hash-committed live internet source retrieved at runtime.

Verifiable by design

Citations, hashes, and NegativeProofRecords are first-class outputs — not audit logs added after the fact.

Governance is non-bypassable

Resource constraints, refusals, and degradation rules are enforced at the substrate level.

Substrate continuity

Node migration preserves identity and all evidence references across hardware boundaries.

Download Tools View Specifications Browse Repos Machine Interface