Genesis / Prototype Stage / GENESIS

One task.
An inspectable trail of evidence.

The first proposed experiment starts with licensed UTF-8 offline text. Its purpose is to test whether coordination, review and recovery hold together.

02 / A bounded beginning

One task.
An inspectable trail of evidence.

The first proposed experiment starts with licensed UTF-8 offline text. Its purpose is to test whether coordination, review and recovery hold together.

Proposed · Design proposal

01Input: UTF-8 offline text, sample_id, permission manifest, rule version and content digest. Freeze inputs before assigning work.
02Execution: A fixed-version Python CPU Runner with read-only inputs. No network access during tasks, no execution of sample code, no wallets or real funds.
03Output: JSON with sample_id, rule_id, match locations, result, parse-failure reason, Runner version and input/output digests.
04Verification: A designated verifier checks permissions, versions and structure, then reviews against reference rules or known answers.
05Acceptance: Passing verification does not trigger automatic acceptance. The coordinator makes a separate decision under the policy frozen before execution.
06Record: Link the result to Task, Attempt, Artifact, Verification and Acceptance, preserving exportable evidence.

A proposed controlled experiment. Not a live public Node network or a production smart-contract audit product.

EVIDENCE / 001

One sample. Four inspectable records.

Edit the synthetic text to explore exact-pattern results and SHA-256 digests. Computation stays in your browser; input is not uploaded. This does not demonstrate an implemented Python Node or protocol service.

Synthetic sample text (up to 4,000 characters)

Local browser illustration

01Input
02Rule
03Artifact
04Verification

Input

Inspect the sample ID, synthetic provenance, permission statement and UTF-8 input digest.

{
  "sample_id": "sample-001",
  "source": "synthetic",
  "license": "illustrative-authorized-input",
  "encoding": "UTF-8",
  "text": "require(tx.origin == owner);"
}

Rule

Freeze demo-1: a case-sensitive search for tx.origin. Comments and strings can also match.

{
  "rule_id": "R-DEMO-01",
  "version": "demo-1",
  "pattern": "tx.origin",
  "case_sensitive": true,
  "position_unit": "UTF-8 bytes",
  "semantic_analysis": false
}

Result

Generate UTF-8 byte positions, the match result and input/output digests without executing sample code.

{
  "sample_id": "sample-001",
  "rule_id": "R-DEMO-01",
  "rule_version": "demo-1",
  "runner_version": "browser-illustration-1",
  "matches": [
    {
      "start": 8,
      "end": 17
    }
  ],
  "result": 1,
  "parse_failure_reason": null
}

Verification

Illustrate local structural and reference-rule checks. There is no real verifier signature, and acceptance has not been decided.

{
  "mode": "local-browser-illustration",
  "reference_check": "not-a-real-verifier",
  "acceptance": "not-decided"
}

A result indicates a text-pattern match only. It is not proof of a vulnerability or a security audit conclusion.

PROTOCOL / 01

Every handoff has a responsible role.

Proposed workflow. Scroll or select a step to explore its inputs, action, outputs and evidence. On mobile, expand ordinary vertical cards.

Synthetic Demo · Not production records

01 / 06

Task Registry

A submitter registers the task

Read the full explanation

Task Registry

A submitter registers the task

Input: Licensed UTF-8 samples, rule version and resource limits.
Action: Check permissions and acceptance conditions; freeze the task definition.
Output: A Task ready for assignment.
Evidence: task_id, input_digest, policy_version.

Illustrative JSON · Not an execution log

{
  "synthetic": true,
  "production_evidence": false,
  "task_id": "synthetic-task-01",
  "state": "registered",
  "input_ref": "sample-001",
  "license_ref": "synthetic-license",
  "rule_version": "demo-1",
  "input_digest": null
}

02 / 06

Coordinator

A coordinator assigns a bounded lease

Read the full explanation

Coordinator

A coordinator assigns a bounded lease

Input: Frozen tasks, available controlled Nodes and permissions.
Action: Lease by capability; record generation, retries and expiry.
Output: A Task Attempt and lease.
Evidence: attempt_id, generation, lease_expires_at.

Illustrative JSON · Not an execution log

{
  "synthetic": true,
  "production_evidence": false,
  "task_id": "synthetic-task-01",
  "attempt_id": "synthetic-attempt-01",
  "node_id": "synthetic-node-01",
  "state": "leased",
  "generation": 1,
  "lease_policy": "illustrative-lease-1"
}

03 / 06

Node Runner

A contributor device reads and runs

Read the full explanation

Node Runner

A contributor device reads and runs

Input: A valid lease, fixed Runner and authorized input.
Action: Process text offline under the designated rule and return structured output.
Output: An Artifact or explicit failure reason.
Evidence: runner_version, input/output_digest, state events.

Illustrative JSON · Not an execution log

{
  "synthetic": true,
  "production_evidence": false,
  "attempt_id": "synthetic-attempt-01",
  "state": "completed",
  "runner_version": "illustrative-runner-1",
  "network_access": false,
  "artifact_id": "synthetic-artifact-01",
  "output_digest": null
}

04 / 06

Verifier

A designated verifier reviews

Read the full explanation

Verifier

A designated verifier reviews

Input: Structured artifact, permissions and reference rule.
Action: Check versions, structure and known answers; distinguish pass, fail and error.
Output: A Verification record.
Evidence: verifier_id, policy_version, evidence references.

Illustrative JSON · Not an execution log

{
  "synthetic": true,
  "production_evidence": false,
  "verification_id": "synthetic-review-01",
  "artifact_id": "synthetic-artifact-01",
  "state": "illustrative-pass",
  "policy_version": "illustrative-policy-1",
  "acceptance": "not-decided"
}

05 / 06

Acceptance

A coordinator decides separately

Read the full explanation

Acceptance

A coordinator decides separately

Input: Valid Verification, task role and frozen acceptance policy.
Action: Decide whether the unique acceptance slot is filled; record the reason.
Output: Accepted, Rejected or awaiting recovery.
Evidence: acceptance_id, policy_version, decision_reason.

Illustrative JSON · Not an execution log

{
  "synthetic": true,
  "production_evidence": false,
  "acceptance_id": "synthetic-accept-01",
  "verification_id": "synthetic-review-01",
  "state": "illustrative-accept",
  "policy_version": "illustrative-policy-1",
  "reason": "separate coordinator decision"
}

06 / 06

Contribution Store

Store evidence-linked contributions

Read the full explanation

Contribution Store

Store evidence-linked contributions

Input: Accepted artifacts and provenance relationships.
Action: Transactionally link the task, attempt, artifact, review and acceptance.
Output: A queryable, revocable contribution index.
Evidence: contribution_id, provenance, revocation.

Illustrative JSON · Not an execution log

{
  "synthetic": true,
  "production_evidence": false,
  "contribution_id": "synthetic-contribution-01",
  "acceptance_id": "synthetic-accept-01",
  "state": "illustrative-recorded",
  "evidence_refs": [
    "synthetic-task-01",
    "synthetic-attempt-01",
    "synthetic-artifact-01",
    "synthetic-review-01",
    "synthetic-accept-01"
  ],
  "economic_rights": false
}

01 / 06

Task Registry

A submitter registers the task

Input: Licensed UTF-8 samples, rule version and resource limits.
Action: Check permissions and acceptance conditions; freeze the task definition.
Output: A Task ready for assignment.
Evidence: task_id, input_digest, policy_version.

Illustrative JSON · Not an execution log

{
  "synthetic": true,
  "production_evidence": false,
  "task_id": "synthetic-task-01",
  "state": "registered",
  "input_ref": "sample-001",
  "license_ref": "synthetic-license",
  "rule_version": "demo-1",
  "input_digest": null
}

Dashboard — A submitter inspects the evidence. An inspectable task view.

CURRENT STATUS

A clear account of where we are.

The website and documents are public. Prototype capabilities still need execution evidence.

Public now

Official bilingual website
Litepaper and Whitepaper
Browser-based synthetic illustrations
Proposed protocol and data structures

Planned validation

G0 single-machine closed loop
Python Runner and designated verifier
Database storage and evidence exports
Retry, cancellation, revocation and recovery tests

Not available yet

Public Node client and network
Live operational Dashboard
Permissionless task marketplace
Native Token, TGE, earnings or airdrop arrangements

G0 — G5

Advance on evidence.
Not a countdown.

All stages below are Planned. Each must answer a concrete question. Status does not advance without acceptance evidence.

Highlighting indicates your reading position, not a stage that has passed acceptance.

Single-machine loop

Planned

Core question: Can one complete task chain run?
Minimum artifact: Frozen task package, Runner, verifier, database and evidence export.
Pass condition: Reproducible end-to-end flow from licensed input to acceptance; traceable errors.
Failure response: Narrow the task, fix state and evidence gaps, then rerun.

Real multiple devices

Planned

Core question: Does execution and recovery work across devices?
Minimum artifact: Independent device versions, attempts, retries and rerun records.
Pass condition: Reproduce the same task across devices; disconnects and duplicate submissions do not duplicate acceptance.
Failure response: Pause expansion; examine environments and lease policy.

Views and evidence exports

Planned

Core question: Can someone else inspect and review the result?
Minimum artifact: Task views, provenance, revocations and verifiable exports.
Pass condition: An external reviewer can reconstruct acceptance reasons from the export.
Failure response: Fix missing links and access control, then export again.

External repeat use

Planned

Core question: Does a real team choose to use it again?
Minimum artifact: An authorized external task and feedback from a second use.
Pass condition: A requester returns and identifies concrete, verifiable value.
Failure response: Redefine the use case; signup counts do not replace usage.

Cost and reliability

Planned

Core question: Is the end-to-end cost sustainable?
Minimum artifact: A ledger including failures, transfer, review, labor and recovery.
Pass condition: Complete the same task batch within frozen budgets and reliability goals.
Failure response: Adjust the workflow or discontinue unsustainable task types.

Openness and economics

Planned

Core question: Is wider participation necessary and controllable?
Minimum artifact: Security review, responsibility arrangements, compliance findings and economic-necessity analysis.
Pass condition: Evidence supports access expansion, real demand and risk boundaries.
Failure response: Retain controlled participation; introduce no native Token without necessity.

One task.An inspectable trail of evidence.