Open the Admin client
Go to the internal Admin interface and select the relevant client or Business Unit.
Approved context and task notes
Context Management
How Jessie separates approved client context, retrieved evidence, and task-specific consultant notes.
Context Types
| Type | What it means | How Jessie uses it |
|---|---|---|
| Approved client context | Reviewed client facts, rules, strategy, priorities, measurement notes, and source references. | Injected into skill prompts and used to judge performance in context. |
| Retrieved context chunks/facts | Prompt-ready slices from the R2-backed client context lake and D1 context facts. | Loaded at run time through the context retrieval interface. |
| Task-specific consultant notes | Instructions and caveats on the Asana task or follow-up comments. | Guide the current run only; do not become durable truth automatically. |
| Live evidence | Fresh or configured source data from GA4, Search Console, Ads platforms, Browser Run, R2, or D1. | Grounds the report or audit. |
| Generated output | Reports, comments, attachments, evidence JSON, and planning checkpoints. | Reviewed by a human before client use. |
Agent Context Folder
Each client or Business Unit that Jessie works on should have a maintained Box Agent Context folder. This is the consultant-maintained source of truth for client context that Jessie can use.
| Responsibility | What to do |
|---|---|
| Create the folder | Create or confirm a Box folder named Agent Context inside the client or Business Unit context area. |
| Grant access | A Box admin or folder owner must make the folder accessible to the AgentOS Box service account. The system checks access through the configured Box binding. |
| Keep it curated | Store approved briefs, rules, strategy notes, current priorities, measurement caveats, and other context Jessie should rely on. |
| Remove or replace stale material | Outdated files should be removed, archived outside the folder, or replaced with clearer current context so future runs do not inherit old assumptions. |
| Promote generated output deliberately | A Jessie report, Asana note, or generated artifact is not trusted context just because it exists. It becomes source context only when a human deliberately adds the approved version to the Agent Context folder. |
Consultants should maintain the Box folder, not D1 rows, R2 objects, chunks, embeddings, or derived facts. Those are system-managed cache/index layers behind the context retrieval interface.
Admin Configuration
The folder is not usable by Jessie until it is linked to the Business Unit in the Admin interface.
Open the Context tab
The Context tab owns the Business Unit context source binding.
Enter the Box folder
Paste the Box Agent Context folder URL or numeric folder ID.
Save the binding
The Worker validates and normalizes the folder reference, then stores the Context Source Binding in D1.
Test Access
Use Test Access to confirm the AgentOS Box service account can list the configured folder.
Refresh context
Run the context refresh so the system scans the folder, records the manifest, downloads supported text files, writes chunks to R2/D1, and creates a prompt-ready Context Pack when usable content exists.
| Admin state | Meaning for Jessie |
|---|---|
| No active Context Source Binding | Context-dependent Jessie work should block or ask for setup instead of producing context-free recommendations. |
| Access test failed | The Box folder exists in Admin, but the AgentOS service account cannot read it yet. Fix Box permissions before relying on it. |
| Refresh completed without prompt-ready chunks | The folder was scanned, but current supported content was not available for prompts. Add supported text/markdown context or wait for parser coverage. |
| Prompt-ready current Context Pack | Jessie can retrieve relevant context chunks/facts from the current pack during task execution. |
Context Flow
Consultants maintain Agent Context
Box remains the business-maintained source of truth through the configured Agent Context folder.
Admin links the folder
The Business Unit Context tab stores the active Box Context Source Binding and verifies service-account access.
Context ingestion prepares runtime access
The context lake extracts and indexes prompt-ready chunks and facts without giving the model unrestricted memory.
Jessie resolves the Business Unit
The task is matched to a configured Business Unit and its source assets.
Prompt capsule is assembled
Approved context, consultant notes, and evidence are compacted for the selected skill.
AI Gateway synthesis runs
The model receives bounded context and evidence, then returns the insight layer.
Output distinguishes sources
Reports should separate approved context, task notes, data evidence, and caveats when material.
Conflicts
Data in isolation is not enough. A CPA increase may be expected if the client approved scaling spend; a conversion drop may be inconclusive if lead quality is still being reviewed. Jessie should call out material conflicts instead of flattening them.
- If task notes conflict with approved context, Jessie should mention the conflict and ask for clarification when it affects the conclusion.
- If data conflicts with context, Jessie should explain the mismatch and suggest follow-up checks.
- If context is missing, Jessie should say what context was unavailable instead of pretending to know it.
- If a consultant wants a task note to become durable context, it needs a separate context update path.
Governance
- Box Agent Context folders remain the consultant-maintained source of truth for client context documents.
- The Admin Registry Business Unit Context tab is the source of truth for which Box folder Agency OS should ingest.
- A context refresh is required before new or changed Box files become prompt-ready runtime context.
- R2 and D1 provide prompt-time context retrieval, not an unrestricted model memory store.
- AI Gateway payload logging remains bounded by policy; D1 stores compact run-step metadata rather than raw provider payloads.
- Generated output can propose context updates, but Jessie must not silently rewrite trusted context.