← All products
liveAgent systems

Product Seven | £19 AI company-brain add-on

Context Atlas for Founders

A £19 founder decision layer for Product 5 that turns reviewed company evidence into one choice, one bounded agent workflow, one 30-day test and six usable files.

Use Product 5 to approve the facts. Use Product 7 to compare options, record the founder decision and return measured evidence.

The worked example answers a practical founder question: test a support contractor for 30 days before committing to a full-time hire.

What you receive
  • A readable three-option founder decision workspace
  • Six decision, risk, test and agent-harness files
  • A direct Product 5 → Product 7 → Product 5 evidence loop

Runs from the downloaded folder. No hosted account is required.

£19 launch priceOne-time founder add-on · Product 5 sold separately
  • One practical founder decision
  • Three bounded agent roles
  • £0 agent spend authority
  • Six paid files

Review company truth in Product 5. Make the decision in Product 7.

Product 5 approves the support volume, response time, founder time and runway facts. Product 7 compares three options, records a 30-day contractor test, assigns three bounded agent-harness tasks, sets £0 autonomous agent spend and returns the measured result.

  1. 1Product 5Approve four source-backed company facts.
  2. 2Product 7Compare founder-led, contractor and full-time options.
  3. 3Bounded delegationAgents read, propose or verify only inside their task packets.
  4. 430-day testMeasure response time, founder time, cost and quality.
  5. 5Back to Product 5Review the receipt before company truth changes.

Use Product 5 to know the company. Use Product 7 to make one founder decision.

Product 5 supplies the reviewed baseline. Product 7 compares the real options, records the founder-owned choice, defines the 30-day test and packages bounded tasks for people or agent harnesses.

1. Review in Product 5
Approve the support volume, response time, founder time and runway sources.
2. Decide in Product 7
Compare founder-led support, a contractor test and a full-time hire; choose the smallest reversible move.
3. Delegate safely
Give each agent harness a small task packet with declared authority, inputs, outputs and stop conditions.
4. Return the evidence
Send measured response time, founder hours, cost, quality and customer feedback back to Product 5.

Files passed through the workflow: Product 5 sources → six-file founder decision pack → decision receipt.

One complete founder decision system—not another vague company map.

  • A worked answer to: should we hire customer support now?
  • Four approved Product 5 facts and three consistently compared options
  • A capped 30-day contractor test with response-time, founder-time, cost and quality gates
  • Three bounded agent-harness roles with explicit tasks, reads, writes, stop conditions and expected results
  • A founder-set cost boundary that separates existing subscription cost, £0 autonomous agent spend and the £1,200 human-contractor test cap
  • Six founder-relevant files that keep hiring, candidate outreach and uncapped spend unauthorised

Every file in the six-part founder pack, explained.

The public demo shows the structure and purpose of all six paid files without giving away the buyer ZIP.

01

Founder decision brief

founder-decision-brief.md

Records the question, approved facts, chosen action, owner, rationale and what remains unauthorised.

02

Options scorecard

options-scorecard.md

Compares founder-led support, a contractor test and a full-time hire across the same five criteria.

03

Risk register

risk-register.md

Names the assumptions, failure modes, mitigations and evidence request behind the decision.

04

30-day test plan

thirty-day-test-plan.md

Defines the weekly tasks, success gates, measurements and day-30 review.

05

Agent harness task packet

agent-harness-task-packet.json

Defines evidence, planning and verification roles with explicit permissions, stop conditions and founder approval gates.

06

Decision receipt

decision-receipt.md

Captures the measured result and proposes source-linked updates back to Product 5.

The example starts with a founder decision you can understand in seconds.

Support is consuming 11 founder hours per week, but 10 months of runway makes a permanent hire risky. Product 7 compares three options and chooses the smallest test that can return evidence.

PACK: RELEASE READINESSReviewed

Decide whether to hire customer support now

Included
4 approved Product 5 facts
Connected
Facts → options → decision → 30-day test → evidence return
Provenance
Support export, time audit, cash forecast, decision criteria and test-readiness review

Constraints carried into the task

  • Cap the test at £1,200
  • Do not authorise a permanent hire
  • Protect support quality
  • Return measured results to Product 5

UncertaintyThe contractor may not return six founder hours or maintain response quality.

ExcludedNo hiring, candidate outreach, employment offer, uncapped spend, publication or software work is authorised.

Shared foundation · Context Atlas familyFounder edition

Follow one practical founder question from reviewed company evidence to an option comparison, decision and evidence receipt.

Start in Context Atlas with reviewed company sources. Open one founder question here, compare the real options, export six decision files, then return the measured result to Context Atlas for review.

Context packetWorked company example
Local preview

A worked founder decision that shows exactly what the £19 add-on does.

Product 7 turns four reviewed Product 5 facts into a three-option comparison, a reversible 30-day decision and a measurable evidence return.

4
approved Product 5 facts
3
options compared consistently
3
bounded agent-harness roles
6
files in the paid pack

How you use both products on a real founder decision.

The founder pack carries reviewed truth into one decision. Response time, founder hours, cost, quality and customer feedback come back as proposed evidence—not automatic company truth.

  1. 01

    Review in Product 5

    Accept the four company facts and preserve the source and human review behind each one.

  2. 02

    Compare in Product 7

    Score three options across cost, speed, founder time, commitment and evidence gaps.

  3. 03

    Delegate bounded tasks

    Route evidence, planning and verification packets to subscribed agent harnesses without transferring founder authority.

  4. 04

    Run the bounded test

    Measure response time, founder time, cost, support quality and customer feedback for 30 days.

  5. 05

    Return evidence to Product 5

    Review the decision receipt before accepted company truth or the next hiring decision changes.

Use the founder decision pack with the system you already trust.

Compatibility language is intentionally exact: mapped architecture is not presented as live acceptance.

Neutral Markdown

Six-file pack validated

All six founder deliverables are readable without a graph tool or technical setup.

Browser-local pack

Six-file contract tested

The buyer-mode viewer creates an inspectable ZIP locally. The public demo previews the files without releasing that ZIP.

Agent harnesses and knowledge-graph tools

Portable task packet included

The JSON packet declares three roles, allowed reads and writes, stop conditions, expected results and founder approvals without depending on one vendor.

ChaseOS

Public governance pattern included

The example follows public ChaseOS Core task-packet, role-scope, approval-gate and evidence-receipt concepts. Private-instance integration remains separate and unverified.

Inspect the workflow, decision workspace, and deliverables at readable size.

Choose a guided step, then click the preview itself to open the complete working Product 7 workspace. Use the secondary still-image control only when you want to inspect one frame.

Short walkthroughSee the workflow move from reviewed sources to a founder decision pack.
Context Atlas founder workflow linking Product 5 evidence review to Product 7 decision and back to Product 5

What this product is, and what it is not.

Why is Product 7 £19 when Product 5 is £39?

Product 5 is the reusable evidence foundation. Product 7 is a smaller founder decision layer that depends on that foundation, so its launch price is deliberately lower.

What does Product 7 add to Product 5?

Product 5 reviews sources and trust states. Product 7 compares options, records one founder decision, defines the test and exports six decision-specific files.

Does Product 7 require Product 6?

No. Product 6 is optional and only receives a bounded task if the founder later authorises software work.

Will business AI hire or contact candidates?

No. The pack explicitly prohibits hiring, candidate outreach, employment offers and spend unless a human separately authorises them.

How does this work with several agent subscriptions?

Product 7 treats each agent harness as a bounded worker. The included task packet gives the evidence analyst, operations planner and verification harness separate permissions and expected results. A subscription provides access to the worker; the founder still owns every protected decision.

Is this connected to a private ChaseOS instance?

No. The example uses public ChaseOS Core concepts—task packets, role scope, approval gates, handoffs and evidence receipts—without reading private company state or claiming a tested private adapter.

Is the support-hiring example a real company case?

No. The support counts, runway and costs are fictional worked data. The decision workflow is the product; the example is not a customer-result claim.

Can a non-technical founder use it?

Yes. The demo uses a readable decision memo, option cards and plain-English file previews. No graph interpretation or coding is required.

Version 1.0 is available for £19 through ChaseInTech direct checkout.

ChaseInTech direct checkout is secured by Stripe, with the download released only after the payment session is verified.

The founder add-on is £19 once because Product 5 supplies the £39 evidence foundation. ChaseInTech direct checkout uses Stripe and releases the verified Version 1.0 archive only after the paid session passes server-side checks.