Skip to content
gigiac. BRAINExplore My Use Case

GIGIAC BRAIN

Your company’s second brain. Built for AI work.

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.

ONE QUESTION. TWO WAYS.
SOURCES
Pricing
Brand guide
Architecture
Decisions
Support
Security

Read everything.
Rebuild the brief.

All six documents.
Every request.

AGENT INPUT
All six documentsThe whole library, again

Another question. The same reading, all over again.

INTELLIGENCE THAT COMPOUNDSLESS REDISCOVERY. MORE FORWARD MOTION.EXPLORE ↓

A SECOND BRAIN WITH A JOB TO DO

Keep the knowledge.
Put it back to work.

A useful company memory should help someone take the next step, not just save another summary.

THE ADVANTAGE

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.

THE ADVANTAGE

Keep the evidence.

A short answer should have a path to the source.

Context Capsules are designed to connect useful facts and decisions to supporting material. Go deeper when the task needs it.

THE ADVANTAGE

Make reuse count.

Find out whether reuse pays off.

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

You kept the notes.
The next agent starts cold.

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.

THE PATTERN TO CHANGE
Different agents. The same work, again.

Each agent searches, reads and reconstructs the same knowledge.

FROM KNOWLEDGE TO WORKING MEMORY

A compact brief.
A path to the full story.

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.

  1. Bring together the documents, conversations and code your agents are allowed to use.

  2. Organize decisions, constraints and relationships. Keep each important claim linked to its source.

  3. Create compact, reusable context with a path back to the full evidence.

  4. Give authorized agents relevant context at the right depth, without repeating the whole briefing.

  5. Review new decisions and useful results before adding them to shared memory.

THE CONTEXT ENGINERaw information
Raw information

pricing-policy.md / release-notes / project-decisions

MAKE THE ECONOMICS ADD UP

Run your numbers.
Count every cost.

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.

YOUR WORKLOAD
Model pricing & provider caching

Expansion tokens use the uncached price. Current tokens should include all input already used by the baseline workflow.

All-in costs & successful work

Enter your prices and workload. Include retries in run counts.

YOUR COST ESTIMATE

Potential net savings / month$7,717

43.2% lower total modeled cost, including setup allocation.

Current workflow$17,860
With reusable context$10,143
Successful work / dollar1.76×relative to current workflow
Break-even workload85,114runs / month, quality-adjusted
PROPOSED$10,143

Where the
budget goes.

Every modeled cost.
One total to compare.

Reusable input
$2,460
Deeper retrieval
$1,200
Output, both scenarios
$2,500
Maintenance + platform
$1,900
Setup allocation
$2,083

Cost per successful run

Current$0.0794
Proposed$0.0451
Setup payback2.6 months
Assess your real workload
Transparent math. Every cost accounted for.

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

A different model.
The same company knowledge.

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.

A PORTABLE CONTEXT LAYER
GIGIAC BRAIN

Your organizational memory

Decisions & history

What we know. Why we chose it.

Policies & constraints

How the organization works.

Sources & evidence

The knowledge behind the answer.

Same memory. A different consumer.

Choose an example model role

CONTEXT REQUEST / ENGINEERING

Plan the next release.

Architecture decisions, project constraints and release policies.

Relevant capsules from the same shared memory

CONTEXT AT THE DEPTH THE TASK NEEDS

Essentials first.
Evidence on demand.

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

Pricing policyApproved service rate · v3
$2,000
Brand guideVoice and language · v2
Proposal historyPast decisions and constraints
CONTEXT CAPSULEEXAMPLE

Same knowledge.
The right depth.

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.
Start compact. Retrieve evidence when needed.

MEMORY WITH A PURPOSE

Keep what matters
for the next task.

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.

RETENTION EXPLORER
EXAMPLE CAPSULEShort-term

This quarter’s proposal

Keep working context available while a project is moving.

30days inactive
FIVE MEMORY TIERS

Rings show the time remaining in each tier. Core stays protected.

Retained for reuse

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

When the facts change,
the context should too.

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.

  1. Notice the change.

    An approved source is updated.

  2. Trace the impact.

    Find the capsules that depend on it.

  3. Refresh or review.

    Rebuild affected context and flag conflicts.

  4. Reuse the update.

    Serve the approved version to authorized agents.

MEMORY YOU CAN EXAMINE

Keep the source.
Keep the boundaries.

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.

THE ANATOMY OF TRUSTED CONTEXTDESIGN PRINCIPLES

Source-grounded

Trace important context back to supporting evidence.

START WITH THE KNOWLEDGE YOU KEEP REUSING

Find a useful role
for your company’s second brain.

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.

  1. Review your spend

    Start with the work your agents repeat.

  2. Benchmark the task

    Compare cost, quality and completion time.

  3. Scope a pilot

    Define the workflow and the comparison.

  4. Measure the return

    Evaluate the result before expanding.

FOR YOUR ORGANIZATION

Explore a brain for your team.

Tell us where company knowledge gets explained or reconstructed again. We can explore whether an assessment or pilot fits your workflow.

Prefer email? Contact Gigiac.

FOR BUILDERS & TEAMS

Be ready for Brain.

Join the interest list for release updates and potential pilot opportunities for your team.

Prefer email? Contact Gigiac.

THE STANDARD THAT MATTERS

More valuable work.
For every dollar
you spend on AI.

INTELLIGENCE THAT COMPOUNDS

Give what you know
another chance
to be useful.

Explore a shared brain for the work your team does next.

BEFORE YOU CHOOSE

Get clear
on the details.

How could Gigiac reduce inference costs?

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.

Will my agents be faster or more accurate?

Less context reconstruction can give agents a faster start. Use a representative workflow to compare completion time, answer quality and total cost together.

What carries over when I switch models?

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.

How is this different from prompt caching?

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.

Is this a second brain for a person or a company?

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.

What happens when a source changes or memory expires?

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.

What does an enterprise deployment cost?

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.

How do we get started?

Request an assessment with one recurring workflow and the context it needs. Or join early access for release updates and pilot opportunities.