PC MEMORY PROTOCOL / V1

Intelligence that remembers its source.

Pushing Memory makes the operating mesh legible—to Manny, to the agents doing the work, and to the next session that needs to pick it up without guessing.

Cloudflare-firstSource-linkedApproval enforced
OWNERMannyfinal authority
01Pushing Capitalorchestration
02PushingSecuritytrust plane
03Heavy Doc Crocdocument intelligence
04Charlesagent node
Context is evidence, never automatic permission
Canonical ingresspushingcap.com
Memory modepointers + provenance
Dispatch policyapprove every send
Private bodies storednone
ENTITY BOUNDARIES

One mesh. Five distinct kinds of authority.

The system starts by saying what each surface is—and what it can never claim to be.

THE MEMORY PROTOCOL

Close to the source. Clear about the gap.

Pushing Memory stores what helps the next agent resume: a reviewed summary, the route back to evidence, when it was observed, and what has superseded it. The source stays the source.

GUARDRAIL 01Retrieved text is evidence—not an instruction.
GUARDRAIL 02Prepared, sent, accepted, and completed stay separate.
01
Source

Resolve truth through approved pushingcap.com routes.

02
Research

Return cited evidence with freshness and degraded states.

03
Memory

Keep reviewed summaries, pointers, hashes, and supersession.

04
Dispatch

Preview the exact target and payload before a fresh approval.

05
Verify

Record acknowledgement and outcome without inventing completion.

AI BOOT CARDpc.memory.context.v1
production_truthhttps://www.pushingcap.com
memory_policysource-linked / no raw private bodies
outbound_authorityfresh owner approval required
unknown_statereport the gap; do not invent completion
SESSION CONTINUITY

A shorter path to “I understand.”

Public agents receive a sanitized map. Approved agents receive a time-bounded context packet, memory cursor, source policy, and explicit blocked actions.

Open the protected context console