Skip to content

GBrain × AODL: shadow context/attention bridge #112

Open

Description

@kvnloo

Problem

GBrain can supply durable ambient context, but memory evidence must not silently become z0int execution authority or mutate the stable AODL intent contract.

First slice

  • consume GBrain MEMORY_VERBS v1 context_pack / delta
  • preserve GBrain evidence provenance in z0int ContextPacket
  • represent memory participation with existing AODL memory + data primitives
  • keep concrete GBrain runtime/source binding in compiled plan
  • emit shadow-only IGNORE | OBSERVE | PREPARE candidates
  • correlate candidates with normal z0int decision/outcome receipts
  • no action, interruption, write-back, or private-memory widening

Acceptance

  • memory evidence grants no action/interruption authority
  • trusted-local recall is excluded until a scoped/remote transport prevents unredacted private reads
  • AODL intent source hash is stable across GBrain implementation-binding changes
  • deterministic candidate IDs can be joined to existing receipts without changing receipt outcome fields
  • focused tests + full offline CI pass

Follow-up

Use joined receipts to evaluate an attention policy; only then consider SURFACE/Ripple and verified durable write-back.

Credit / provenance

The MEMORY_VERBS v1 / ambient recall contract is from Garry Tan / garrytan/gbrain. AODL memory/intent/plan/observed semantics are existing work in kvnloo/aodl. This issue is an integration/measurement slice, not a redefinition of either contract.

Activity

  1. kvnloo commented on Oct 5, 2026

    @kvnloo
    OwnerAuthor

    Memory/context consolidation lives in #22. This remains the bounded GBrain shadow context/attention bridge, not a second canonical memory store or mandatory runtime dependency. Keep the existing no-writeback/no-authority/private-scope boundaries. A future context_pack/delta consumer should use the shared source/scope/snapshot contract and qualify model-visible use separately; it does not establish universal capture or continuity by itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions