Context Layer

Context Layer / working proposal

Useful context,
without total access.

A proposed protocol for letting apps and agents request only the context a task needs. Raw memory stays behind a user-controlled policy boundary. Every disclosure is scoped, expiring, and receipted.

Run the demo Open the map

One request / progressively reduced

Watch context become a purpose-bound bundle.

  1. 01Requesttask asks
  2. 02Vaultcontext stays private
  3. 03Policyfields reduce
  4. 04Bundleminimum reveal
  5. 05Surfaceresult appears
  6. 06Receiptdecision records

Why this exists

More useful agents should not require more exposed lives.

  1. 01

    Problem

    AI becomes more useful with context. Today, getting that context often means copying private memory into every platform that wants to use it.

  2. 02

    Protocol

    Context Layer keeps private memory behind a policy boundary. Apps request a purpose-bound bundle instead of receiving unrestricted access.

  3. 03

    Proof

    Every interaction should show what was used, who received it, why it was allowed, how long it lasts, and what receipt records the result.

  4. 04

    Status

    This is a working proposal and synthetic demonstrator. It is not an adopted standard, production vault, or security certification.

Synthetic protocol demo

Plan a day without sharing a life.

A fictional itinerary app plans a Saturday in Harbor City. The data is synthetic, stays in this browser, and resets locally.

Scenario / Harbor City Step 1 of 6

Context request

The app declares what it needs and why.

It requests enough context to plan a Saturday, not permission to browse an entire vault.

Requested

Purpose: build a one-day itinerary. Retention: none.

Input5 fields
    Output5 fields
      Disclosure Request defines five fields
      100%
      View protocol data

      Progressive protocol map

      Read one layer at a time.

      The complete architecture remains available as a reference, but this view limits each pass to one responsibility and its current-world equivalents.

      Need the full system view? Open the technical diagram only after the layer model is clear.

      View full diagram Read draft specification

      Protocol guide

      Ask the site to explain or move.

      Text is the default. The guide can answer from this proposal and navigate only to approved sections on this page. Without a configured API, it remains a transparent local guide.

      Local guide Ready

      Guide Ask a protocol question or tell me which part you want to see.

      Reference and status

      A proposal you can inspect.

      The demonstrator traces one request from capture through policy, scoped disclosure, and receipt. The linked documents describe the protocol objects, trust boundaries, and open implementation questions in more detail.

      01Draft technical specificationCore objects, lifecycles, policy, security 02Implementation profilesAdapters, agents, web, mobile, interoperability 03Plain-language introductionWhy the layer exists and who it can serve 04Navigation manifestMachine-readable public sections and actions
      Working proposal

      This site demonstrates intended behavior with fictional data. It does not claim standards adoption, production security, live vault access, or completed interoperability.