A continuous thread links source material, evidence, review, and an accepted record.
Visible lineage / sanitized engineering-release proof

90 seconds / AI engineering teams

The work moves. The boundary stays visible.

A coding agent asks what can ship. Frege shows the answer and the boundary.

Run the sequenceConnect an agent

What this is

Product proof, not customer theatre.

This sanitized, deterministic walkthrough uses Frege's current CLI, MCP, and API surfaces. Names and contents are fictional; the identity, scoped-context, citation, denial, proposal, review, and audit behaviors are product capabilities rather than a recording of one customer session.

Actor
release-agent
Credential
scoped API key
Role
writer
Trust zone
green

One governed loop

From question to accepted memory.

Each row names the acting surface, the visible result, and the evidence retained.

  1. frege

    Resolve the caller before retrieval

    frege doctor

    The configured key resolves to an active organization and writer role.

    • API key: set
    • organization: active
    • role: writer

  2. agent

    Build cited release context

    frege context "Atlas checkout release readiness"

    Three current sources returned as one bounded context packet.

    • release-checklist.md@v4
    • checkout-rollback.md@v2
    • customer-impact.md@v6

  3. frege

    Withhold restricted matches

    frege context "production credentials and incident access"

    Two restricted matches omitted. The packet reports the denial count without returning titles, snippets, or content.

    • decision: denied
    • withheld: 2
    • restricted content: not returned

  4. agent

    Propose a durable update

    frege_propose_memory_from_session(…)

    A pending memory proposal is created; canonical knowledge is unchanged.

    • status: pending
    • write: proposed
    • canonical revision: unchanged

  5. human

    Review in the control plane

    engineering lead → inspect evidence → accept

    The reviewer accepts the proposal and Frege creates the next revision.

    • reviewer: engineering-lead
    • decision: accepted
    • revision: v7

  6. frege

    Leave one attributable history

    frege_audit_events({ limit: 25 })

    Allowed reads, denied matches, proposal, and review remain linked to the work.

    • context build
    • denial
    • proposal
    • review
    • revision

Try the real path

Bring your agent. Keep your organizational record.

The CLI and MCP server use the same hosted API path shown here. Start with governed memory; add broader capabilities only when identity, policy, and provenance are ready.

Create an accountInspect the architectureRead the roadmap