Start here
README.mdTeaches the Product 5 → Product 6 → implementation → Product 5 evidence loop and how to use every file.
← All products
Product Six | Free developer change-impact toolkit
Context Atlas for Developers
A free, worked developer edition that turns reviewed project sources into a cross-stack task a developer or coding agent can actually use.
Review the project in Product 5, trace one approved feature in Product 6, export six implementation files, then return the proof for review.
Inspect the source, trust state and project relationship behind every record before it guides a coding task.
What you receive
- An interactive team-invitation graph spanning six code and service boundaries
- A six-file developer pack generated locally in the browser
- A worked Product 5 → Product 6 → implementation → Product 5 evidence loop
Runs from the downloaded folder. No hosted account is required.
£0Free developer edition
- One worked coding task
- Six downloadable files
- Browser-local ZIP
- No repository upload
Use Product 5 and Product 6 together
Review the project first. Then build one bounded developer task.
In this example, six reviewed Product 5 sources become one Product 6 team-invitation pack. Test and migration evidence returns to Product 5 for review.
- 1Product 5Accept the feature brief and role policy.
- 2Product 6Trace the implementation and unresolved migration.
- 3Developer or coding agentImplement inside the pack's paths and guardrails.
- 4Back to Product 5Review tests and migration evidence before truth changes.
Plain-English guide
Use Context Atlas to review the project. Use Product 6 to build one task.
For the team-invitation example, Product 5 holds six reviewed sources. Product 6 selects the approved feature, traces the systems it touches, and creates a bounded pack for implementation. Test and migration evidence then goes back to Product 5 for review.
- 1. Review in Product 5
- Approve the feature brief and role policy. Keep the legacy membership migration gap uncertain.
- 2. Build the task in Product 6
- Trace database, API, email, UI, audit and test impact. Export the agent brief and proof checklist.
- 3. Return the evidence
- After coding, send exact tests and migration results back to Product 5 as proposed updates for human review.
Files passed between the products: workspace.json → agent-context-brief.md → verification-receipt.md.
What is included
One complete cross-stack developer task, not a vague project-brain diagram.
- A guided graph for the example task: ship team invitations with Admin and Member roles
- A selected path through membership data, invitation API, admin UI, contract and E2E tests, and agent brief
- Visible role and token guardrails, email and audit side effects, and one unresolved legacy-membership migration
- A browser-local ZIP containing README, impact map, agent brief, risk register, verification receipt and workspace JSON
Free download manifest
Every file in the free developer pack, explained.
These are the exact six files generated by the guided example and the job each one performs.
Change impact map
change-impact-map.mdLists the selected cross-stack path, role and token guardrails, side effects and unresolved migration branch.
Coding-agent handoff
agent-context-brief.mdCarries allowed paths, role rules, forbidden actions, reviewed sources and required tests into implementation.
Risk and evidence
risk-evidence-register.mdSeparates reviewed guardrails and local test evidence from the missing legacy-workspace migration proof.
Verification receipt
verification-receipt.mdStates what was checked, what passed and what the example does not claim.
Portable graph data
workspace.jsonProvides source-linked nodes, edges and trust states for people, agents and graph-capable systems.
Actual result included
The example starts with a feature that looks simple but crosses the stack.
Instead of telling an agent to 'add invitations', the pack names every affected system, authority rule, side effect, forbidden action and proof requirement.
PACK: RELEASE READINESSReviewed
Ship team invitations with role-based access
- Included
- 9 visible developer objects
- Connected
- 8 explained connections
- Provenance
- Feature brief, repository map, ADR, API contract, tests and migration audit
Constraints carried into the task
- Only Owners and Admins invite
- Never grant Owner through an invitation
- 24-hour single-use links
- No public signup
UncertaintyLegacy workspaces still require a counted membership migration and backfill receipt.
ExcludedNo deployment, release or production result is claimed.
Context proof, not memory theatre
Follow a real cross-stack feature from reviewed project sources to a bounded implementation pack.
Start in Context Atlas with six reviewed sources. Open one approved feature here, trace every affected system, export the implementation pack, then return the test and migration evidence to Context Atlas for review.
Context packetWorked project example
Local previewFoundation evidence
A worked task that proves why the graph exists.
Team invitations look simple in a ticket but touch data, permissions, email, UI, audit events and tests. The graph prevents a developer or coding agent from treating the API endpoint as the whole feature.
- 9
- visible developer objects
- 6
- files in the free ZIP
- 6
- reviewed source records
- 1
- migration gap still unverified
Product 5 + Product 6 workflow
How you use both products on a real developer task.
The developer pack carries reviewed truth into implementation. Test and migration results come back as proposed evidence—not automatic truth.
- 01
Review in Product 5
Accept the feature brief and role policy; keep the legacy migration gap uncertain.
- 02
Trace in Product 6
Map the task across membership data, invitation API, role policy, email, admin UI, audit and tests.
- 03
Implement from the pack
Give the developer or coding agent allowed paths, security guardrails, forbidden actions and exact proof.
- 04
Return evidence to Product 5
Propose test receipts and migration results for human review before project truth changes.
Portable by capability
Use the project pack with the system you already trust.
Compatibility language is intentionally exact: mapped architecture is not presented as live acceptance.
Neutral Markdown + JSON
Contract example validatedThe Version 0.1 developer example validates against the shared schema with no dangling references.
Coding agents
Capability profile definedContext packets are runtime-neutral. Acceptance for each named agent remains a separate test.
Knowledge-graph systems
Portable graph path definedNodes, edges, sources and trust states can be adapted to graph-capable tools. Named integrations are not certified yet.
ChaseOS
Optional integration mappedChaseOS can consume the same governed context contract, but this edition does not require ChaseOS.
Interactive product preview
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 6 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 developer implementation pack.
Questions before the preview
What this product is, and what it is not.
Is this tied to one coding agent?
No. The core contract is agent-neutral. Runtime adapters are separate, testable compatibility layers.
Does it copy my entire repository into an AI service?
No by default. The product defines context packets and source references. Data movement remains an explicit operator choice.
Why use Product 5 first?
Product 5 is where the team reviews the source records and trust states. Product 6 should not invent project truth; it selects reviewed records for one task and returns new evidence for review.
Can it work with ChaseOS?
Yes as an optional governed integration path. ChaseOS is not required to use the neutral workspace and graph contract.
Need this operating knowledge applied to your own system?
See ChaseInTech services →