Share the context.
Give the next task the decisions behind it.Bring approved company knowledge into the brief. Give each task the history, rules and decisions it would otherwise need to reconstruct.
GIGIAC BRAIN
Your second-brain setup should help the next person and the next agent, too. Explore a shared memory designed to turn company documents, decisions and lessons into reusable context, with the original evidence close at hand.
Company knowledge. Ready for the next conversation.
All six documents.
Every request.
Another question. The same reading, all over again.
Custom payment terms require approval from the commercial lead before a proposal is shared with a customer.
Only this excerpt is added. The remaining full documents stay outside the request.
A SECOND BRAIN WITH A JOB TO DO
A useful company memory should help someone take the next step, not just save another summary.
Bring approved company knowledge into the brief. Give each task the history, rules and decisions it would otherwise need to reconstruct.
Context Capsules are designed to connect useful facts and decisions to supporting material. Go deeper when the task needs it.
Put a value on the knowledge you reuse. Compare the total cost of a completed task, from context preparation through the finished result.
THE GAP BETWEEN SAVING AND USING
Imagine recording the reasoning behind a pricing decision. A month later, an agent writing a proposal has to find those notes, work out what still applies and reconstruct the brief. Saving the information was only the first step.
The value is in making knowledge useful again.
Each agent searches, reads and reconstructs the same knowledge.
FROM KNOWLEDGE TO WORKING MEMORY
The idea behind Context Capsules is simple: turn approved sources into a compact brief of useful facts, decisions and constraints. Start with that brief, then retrieve supporting detail when it matters.
Bring together the documents, conversations and code your agents are allowed to use.
Organize decisions, constraints and relationships. Keep each important claim linked to its source.
Create compact, reusable context with a path back to the full evidence.
Give authorized agents relevant context at the right depth, without repeating the whole briefing.
Review new decisions and useful results before adding them to shared memory.
pricing-policy.md / release-notes / project-decisions
MAKE THE ECONOMICS ADD UP
Start with the example, then enter your workload. Give existing caching its credit. Include deeper retrieval, maintenance and setup. The number that matters is the total cost of a successful task.
Expansion tokens use the uncached price. Current tokens should include all input already used by the baseline workflow.
Enter your prices and workload. Include retries in run counts.
YOUR COST ESTIMATE
43.2% lower total modeled cost, including setup allocation.
Every modeled cost.
One total to compare.
Cost per successful run
Current input cost = runs × current input tokens × blended input rate ÷ 1,000,000. Reusable input uses its own token count and cache coverage. Additional source cost = runs × expansion frequency × extra tokens × uncached input price ÷ 1,000,000. Expansion frequency is a fraction: 20% is 0.2. Extra tokens are added once, not included again in the base reusable context.
The blended rate weights cached and uncached prices by cache coverage. Output uses the same volume and price in both scenarios. Proposed total adds compile, refresh, retrieval, storage, platform, operating costs and setup divided by the selected months. Existing tool and labor costs are assumed unchanged unless added to operating costs.
Cost per successful run divides each total by runs × its success rate. Work per dollar compares those two unit costs. Break-even is the approximate monthly run count where proposed cost per successful run becomes no higher than the current workflow. It includes monthly setup allocation and assumes the same fixed overhead and per-run costs as volume changes. Different success rates can make break-even impossible even when total spending falls. Setup payback instead divides setup by monthly operating savings before setup allocation, without adjusting for quality. There is no payback when operating savings are zero or negative.
YOUR MEMORY SHOULD OUTLAST YOUR MODEL
Keep organizational context separate from the model using it. Portable company memory means less background to rebuild when you evaluate a new provider or bring another agent into the workflow.
What we know. Why we chose it.
How the organization works.
The knowledge behind the answer.
Same memory. A different consumer.
Choose an example model role
Architecture decisions, project constraints and release policies.
Relevant capsules from the same shared memoryCONTEXT AT THE DEPTH THE TASK NEEDS
In this proposal example, start with the approved rate and rules. Open Working for more context, or Deep for the source excerpts. Then change the price and see the example update.
CONNECTED KNOWLEDGE
Prepare a proposal for Northstar Studio. Use the approved $2,000/month service rate. Keep the voice direct, helpful and specific. Custom terms require a human review. Sources: Pricing policy §2; Brand guide §1.
MEMORY WITH A PURPOSE
A debugging note and a security policy shouldn’t run on the same clock. Explore five memory tiers, from temporary working context to Core knowledge protected until an authorized human approves removal.
Keep working context available while a project is moving.
Rings show the time remaining in each tier. Core stays protected.
30 days until the inactivity threshold.
Retention is not freshness. A retained capsule can still need a source update or review.
Sources stay separate. Retiring derived memory does not delete original documents.
KEEP REUSABLE CONTEXT USEFUL
A new price or revised policy can make an old summary misleading. Keep reusable context connected to its sources: notice what changed, find the affected capsules and review conflicts before the next task.
An approved source is updated.
Find the capsules that depend on it.
Rebuild affected context and flag conflicts.
Serve the approved version to authorized agents.
MEMORY YOU CAN EXAMINE
A useful company memory needs more than stored notes. Follow the evidence, define who can use it and keep a clear history of what changed.
Trace important context back to supporting evidence.
START WITH THE KNOWLEDGE YOU KEEP REUSING
Bring one recurring workflow and the company knowledge it needs. Let’s identify where reusable context could help and scope a pilot you can compare against the way that work gets done today.
Start with the work your agents repeat.
Compare cost, quality and completion time.
Define the workflow and the comparison.
Evaluate the result before expanding.
FOR YOUR ORGANIZATION
Tell us where company knowledge gets explained or reconstructed again. We can explore whether an assessment or pilot fits your workflow.
FOR BUILDERS & TEAMS
Join the interest list for release updates and potential pilot opportunities for your team.
More valuable work.
For every dollar
you spend on AI.
INTELLIGENCE THAT COMPOUNDS
Explore a shared brain for the work your team does next.
BEFORE YOU CHOOSE
Reusable context targets the work agents repeat: finding background, reading the same sources and rebuilding a brief. Compare the full cost per successful task, including caching, context maintenance and implementation.
Less context reconstruction can give agents a faster start. Use a representative workflow to compare completion time, answer quality and total cost together.
Shared company context can carry over across supported providers, reducing the background you rebuild. Models differ in capability and output, so compare them on your actual tasks.
Prompt caching discounts eligible repeated inputs. Reusable organizational memory addresses what goes into that input: structured company knowledge with supporting sources, across compatible workflows and providers. The calculator includes both.
The focus is your company: shared knowledge, decisions and context for the people and authorized agents doing the work. An assessment starts with your sources, workflows and access requirements.
The architecture separates source freshness from memory retention: refresh context when its evidence changes, and retire inactive capsules according to their tier. Original source documents stay separate.
Scope and pricing depend on your workload, integrations and security requirements. Start with an assessment to identify the repeated work and the value of a focused pilot.
Request an assessment with one recurring workflow and the context it needs. Or join early access for release updates and pilot opportunities.