Evidence-bound infrastructure for AI

Make AI state explainable before it becomes consequential.

Noesis Epistemic Fabric turns model context into governed state: memory, provenance, current-truth claims, typed adapters, and receipts that let a system show what it knew, when it knew it, and why a transition was allowed.

Self-hosted control layer Revision-aware Vendor-neutral
01Observe current truth
02Bind claims to evidence
03Prepare safe action
04Leave a receipt

The fabric

A small cognitive kernel. Typed boundaries around it.

NEF keeps the core operations stable and composes them through explicit adapters. Every projection is bounded, every claim has a source, and every state transition can be replayed or refused without ambiguity.

01 / KERNEL

Epistemic memory

Store, recall, correct, and supersede memory with subject, visibility, retention, and revision discipline.

02 / PROOF

Evidence DAG

Connect claims to immutable evidence through typed supports, contradictions, derivations, and invalidations.

03 / TRUTH

Current-truth domains

Keep lifecycle, repository, service, milestone, and completion claims attested, expiring, and conflict-aware.

04 / ADAPTERS

Typed capabilities

Wrap the kernel with finite browser, connector, maintenance, and command adapters instead of generic execution.

05 / HANDOFF

NEF Browser

Use an owner-shared, lease-bound tab for bounded observation and action without putting credentials in model context.

06 / RECEIPTS

Replayable decisions

Carry request, policy, revision, authorization, and evidence references through a unified response envelope.

The method

Prove first. Prepare second. Execute only inside a boundary.

  1. 01

    Orient

    Resolve the active workspace, revision, objective, and authority before an answer or action is formed.

  2. 02

    Explain

    Return bounded evidence paths and currentness markers so a claim can be inspected instead of merely asserted.

  3. 03

    Authorize

    Evaluate capability, scope, lease, policy, and evidence as separate gates with explicit refusal states.

  4. 04

    Record

    Bind the result to a receipt and revision so the next session can reconstruct the handoff without chat history.

NEF Browser by Athena Noesis

Credentials stay with the owner. The work stays bounded.

An owner can authenticate in a visible browser and share one exact tab. NEF receives sanitized observations and lease-bound action results—not cookies, passwords, arbitrary JavaScript, or an unrestricted browser handle.

See the write boundary in WriteGuard
Exact origin and navigation binding
Fresh observation before action
WriteGuard decision and receipt
No credential-bearing payloads

Access and downloads

Use the right distribution path for each artifact.

Public contracts and source repositories are available now. Signed NEF adapter and NEF Browser builds remain request-controlled until their release artifacts are published.

01 / API

NEF API schema

Import the current public OpenAPI contract directly into a GPT or client.

Open schema
02 / ADAPTER

NEF adapter

The adapter source lives with NEL; signed distribution packages are issued through evaluation access.

View NEL source
03 / BROWSER

NEF Browser

The browser runtime is being distributed from the Athena Noesis development repository while signed release packaging is finalized.

View development source
04 / WRITE

WriteGuard

Start the free 30-day evaluation from the public WriteGuard page; production licensing uses the hosted checkout.

Download trial
05 / STRIPE

WriteGuard production

The annual production license is handled by Stripe. Payment details never enter NEF or the browser handoff.

Continue to Stripe

Inspect the claim

The architecture is part of the product.

Start with the public contract, then request the independent proof pack for the governed memory and evidence paths.