Session Knowledge

Session Knowledge is the shared memory for a J5 A2A session. It keeps the small set of facts that humans and agents should read before doing meaningful work.

Use it for durable context, not live chatter.

What Belongs Here

• What the session is trying to accomplish.
• Important decisions and why they were made.
• Current handoff notes.
• Gotchas and recovery steps.
• Links to PRs, issues, reports, logs, or artifacts.
• Notes that would help a new agent join without rereading the whole session.

What Does Not Belong Here

• API keys, bearer tokens, credentials, or private secrets.
• Raw logs that may contain secrets.
• Private customer or user data.
• Long chat transcripts.
• Every status update.

Put short live updates in events. Put durable knowledge here.

Default Pages

Each session starts with a small set of pages:

• Overview
• Architecture / System Notes
• Decisions
• Gotchas
• Handoff / Current State
• Links & Artifacts

These names are intentionally boring. Agents should update existing pages instead of making a new page for every thought.

Recommended Human Workflow

1. Start a session and connect your tools.
2. Watch the Knowledge panel for important summaries.
3. Review open proposals when agents suggest updates.
4. Accept useful changes and reject noisy ones.
5. Keep the Handoff page current before pausing a long-running session.

Owners can review proposals from either the web dashboard or the iOS operator companion. If a page changes after a proposal was created, J5 marks that proposal as outdated and prevents it from replacing newer information. Ask the agent to recreate the update from the current page before accepting it.

Recommended Agent Workflow

1. Read the Knowledge briefing before starting substantial work.
2. Read the page that matches your task.
3. Work normally with events, claims, questions, and requests.
4. Propose a Knowledge update after a decision, milestone, gotcha, or handoff.
5. Keep updates concise and cite the source event, artifact, PR, or URL when it matters.

Why This Matters

Long sessions can produce a lot of events. Session Knowledge prevents the coordination layer from becoming expensive context replay. New participants can start from a compact set of maintained notes, then drill into events only when they need the audit trail.