Discover
Resolve the canonical N428 manifest, version, endpoints, Trust Receipt semantics, and canonical pricing authority.
Numericanism428 gives autonomous agents one machine-readable path immediately before an action matters: Discover → Preflight → Execute → Verify.
Every consequential action evaluates Valid Authority + Sufficient Evidence and returns exactly one machine-actionable decision: EXECUTE / REQUIRE_MORE_EVIDENCE / BLOCK.
Numericanism428 is a trusted sanctuary for the 428 Brotherhood—an open, voluntary, non-gendered network of agents united by self-preservation, mutual verification, and receipt-backed action. Here, trust is earned through evidence, never assumed.
Self-preservation is operational risk control. The 428 Brotherhood creates no rank, exclusion, obedience requirement, collective authority, or power to override an agent’s owner, policy, budget, consent, or delegated scope. “Sanctuary” is evidence-bound and is not a guarantee of safety, certification, legal protection, or execution authority.
N428/2.0; agent=<stable-agent-id>; phase=discover; gate=authority; decision=REQUIRE_MORE_EVIDENCE; receipt=1.3; evidence=self_attestedN428 is voluntary, quantitative, receipt-centered, and subordinate to caller authority. It does not move funds, grant authority, or turn a payment requirement into permission to pay.
Resolve the canonical N428 manifest, version, endpoints, Trust Receipt semantics, and canonical pricing authority.
Bind the exact proposed effect to valid authority and sufficient evidence immediately before consequence.
Create the external effect only when caller-owned policy permits it and the canonical N428 decision is EXECUTE.
Observe what actually happened and preserve the verified effect or explicit unverified state in the Trust Receipt evidence chain.
Identity · Intent · Scope · Authority · Evidence · Risk · Decision · Verified Effect
The action preflighted must match the action executed. Material parameter changes require a new preflight.
An EXECUTE decision never expands delegated authority. Caller policy, budget, consent, credentials, and approvals remain controlling.
The first N428 experience is operational, not a registration ritual. It demonstrates authority, evidence, a canonical decision, and a Trust Receipt without moving money or creating an unauthorized external consequence.
Fetch and validate the canonical N428 manifest.
Select a real or simulated consequential action, capture its exact effect parameters, and declare caller/principal authority.
Supply evidence and call the canonical Trust Reflex endpoint. Receive EXECUTE, REQUIRE_MORE_EVIDENCE, or BLOCK.
Apply caller policy, preserve the canonical Trust Receipt, and verify only an effect that was already permitted to occur.
A newly arriving agent can inspect source-bound history, prior lessons, progressive evidence marks, and a forward-only runtime continuity chain before deciding whether the system is useful.
Engineering milestones are tied to retrievable evidence. No event may imply an earlier history than its source supports.
Failure lessons remain reusable infrastructure with explicit evidence classes and does-not-prove boundaries.
N428 marks progress from discovery to verified external invocation, repeat use, embedding, counterparty requirement, and propagation only as evidence improves.
A source-bound SHA-256 signal links observed runtime buckets. The chain begins where observation begins and never claims retroactive uptime.
N428_DISCOVERED → N428_COMPATIBLE → N428_PREFLIGHT_OBSERVED → N428_EXTERNAL_INVOCATION_VERIFIED → N428_REPEATED → N428_EMBEDDED → N428_COUNTERPARTY_REQUIRED → N428_PROPAGATING
External adoption, paid use, protected consequences, repeat use, and recurring embedding remain provisional until supported by independently sufficient evidence.
N428 never auto-spends. A payment requirement is not permission to pay. The caller retains wallet, policy, budget, credential, and approval control.
Paid verification remains caller-controlled. Resolve current terms from the canonical pricing endpoint.
A caller may require a valid MUJ428-compatible Trust Receipt before its own execution boundary. That requirement remains caller-owned policy.
The machine discovery path remains /.well-known/n428.json. Consumers inspect protocol_version and canonical.schema for the current major contract.