SwiftCNS Docs
SwiftCNS Docs
Install SwiftCNS, take an idea to a recorded decision from the AI tool you already use, and learn the method behind it.
Before you start
SwiftCNS is decision infrastructure for teams building with AI. You describe an idea in your AI tool (Claude, ChatGPT, Cursor, Claude Code, Codex or any MCP client). SwiftCNS finds the assumptions it rests on, designs the experiment and holds you to success criteria you approved before it ran. You call the result and make the decision; SwiftCNS keeps it as a Decision Record, so your next decision starts from your last one.
You need a SwiftCNS account and an AI tool that supports MCP. MCP is included on every plan.
Steps
Install
Create your workspace and connect your AI tool. Install SwiftCNS.
Test
Describe your idea. SwiftCNS proposes assumptions and experiments; you choose, approve the success criteria, run the experiment and log the evidence. Your first test.
Decide
You call the result (Met, Not met or Unclear), write what you learned, and choose: Move forward, Change course, Test again or Drop it. SwiftCNS keeps the record.
Who does what
| SwiftCNS | You |
|---|---|
| Proposes assumptions, scored for importance and evidence | Choose what to test |
| Designs experiments with success criteria | Choose one, assign it, approve it |
| Suggests how to track the evidence | Run it and log the results |
| Drafts observations and insights from the evidence | Call the result and write what you learned |
| Keeps the record, linked end to end | Make the decision, and say why |
Work in two windows: ask in your AI tool, and keep SwiftCNS open beside it to watch each step land. Best practices.
What you get
A Decision Record your team and your AI tools can read later. Here is the one from the example used throughout these docs:
Decision Recordsample data
Should we build the $79/month Team plan?
- assumption
Trial teams that try to invite a teammate will pay $79 a month for a shared workspace.
- experiment
Paid Team offer at invite: when a trial team clicks invite, offer the first month of a shared workspace for $79 through a payment link, and set up sharing by hand for teams that pay.
- success criteria · fixed on approval
At least 3 of the first 15 trial teams that see the offer pay $79 within 7 days of seeing it.
- evidence
4 of 15 teams paid within 7 days; a fifth paid on day 10. Every team that paid had invited 3 or more teammates.Met
- learning
Trial teams will pay to share. Teams of three or more are the ones paying; two-person teams said $79 is too much for two people.
Move forward
Build a minimal billing path for the $79 Team plan and keep setting up sharing by hand until it's automated. Track whether paying teams renew after the first month, and test a lower price for two-person teams separately.
Recorded by the experiment owner · sample data
Done when
- You know where to start: Install, then your first test.
- You know where to look things up: the method, using the app, and working with your AI tool.
For agents: MCP tools and gotchas
- Every page has a Markdown version at
/llms.mdx/docs/<slug>/content.md; the full site is at/llms.txtand/llms-full.txt. - Start with
list_workspaces, thenlist_projects. Workflow authority is in tool results (get_conversation_progress), not in prose. - SwiftCNS proposes; the user chooses. Never set a Learning result or record a Decision unless the user tells you to.