context layer / working proposal
a proposed protocol for letting apps & agents request only the context a task needs. raw memory stays behind a user-controlled policy boundary. every disclosure is scoped, expiring & receipted.
one request / progressively reduced
watch context become a purpose-bound bundle.
why this exists
AI becomes more useful with context. today, getting that context often means copying private memory into every platform that wants to use it.
context layer keeps private memory behind a policy boundary. apps request a purpose-bound bundle instead of receiving unrestricted access.
every interaction should show what was used, who received it, why it was allowed, how long it lasts & what receipt records the result.
this is a working proposal & synthetic demonstrator. it is not an adopted standard, production vault, or security certification.
synthetic protocol demo
a fictional itinerary app plans a Saturday in Harbor City. the data is synthetic, stays in this browser & resets locally.
context request
it requests enough context to plan a Saturday, not permission to browse an entire vault.
purpose: build a one-day itinerary. retention: none.
progressive protocol map
each layer shows what enters, what stays private, how policy reduces scope & which evidence the exchange records.
need the full system view? see capture, policy, scoped disclosure, action & writeback in the complete architecture.
protocol guide
ask about policy, bundles, receipts or the demo. the guide explains the proposal & can jump to the relevant section.
guide ask a protocol question or tell me which part you want to see.
reference & status
the demonstrator traces one request from capture through policy, scoped disclosure & receipt. the linked documents describe the protocol objects, trust boundaries & open implementation questions in more detail.
this site demonstrates intended behavior with fictional data. it does not claim standards adoption, production security, live vault access, or completed interoperability.
