Evidence index and cards
Dated artifacts from Git, tickets, evals, docs, meetings, logs, finance, and payroll stay traceable.
For Atlantic Canadian software founders
The SR&ED operating system for evidence-first teams
A practical workspace for preserving technical facts, source evidence, approvals, and advisor-ready drafts while your startup is still building.
5
Operating phases
14
Day setup plan
17
Workflow skills
61
Workspace templates
Why it exists
Built for the founder who cannot afford a year-end archaeology project
Early teams know the hard technical work when it happens. By filing season, the source links, eval failures, tradeoffs, and approvals are scattered. This repo gives the team a small operating rhythm before that context disappears.
During the sprint
Capture as it happens
Technical uncertainty, experiments, failures, model evals, decisions, and the evidence that proves when they happened.
During the month
Review what holds up
What is accepted, excluded, weak, blocked, sensitive, or waiting on finance, privacy, CTO, or advisor input.
Before advisor review
Hand over a clean binder
Source-backed narratives, cost support, privacy decisions, approval status, and the unresolved questions.
Start with the company, then let evidence drive the story
01
Confirm the company and claim period
Company profile, fiscal period, owners, policy refresh status, and human approval gates.
company-profile.md02
Map systems of record before scanning
Repos, tickets, docs, eval systems, payroll, accounting, and customer evidence restrictions.
inventory-runbook.md03
Run the founder and CTO intake
Turn hard technical work, failed paths, customer context, and routine exclusions into reviewable notes.
first-time-founder-intake.md04
Track uncertainties, experiments, and AI evals
Connect each technical unknown to attempts, tests, datasets, metrics, failure analysis, and dated artifacts.
experiment-ledger.md05
Review people, finance, privacy, and exclusions
Costs, locations, grants, cloud usage, customer data, sensitive IP, and routine work stay visible for review.
finance-evidence-ledger.md06
Build the binder from approved facts only
Package the claim period for a CPA or SR&ED specialist without hiding weak evidence or open questions.
final-review-binder.mdWhat it produces
A source-linked workspace that can survive scrutiny
Each artifact answers a question the claim process will eventually ask. Facts, interpretation, approvals, and sensitive raw material stay in separate lanes.
Control board
Claim question index
The founder control board for what is answered, blocked, excluded, or waiting for human review. One place to see where the whole claim stands.
Experiment ledger
Hypotheses, attempts, tests, results, and conclusions tied to the technical unknown being investigated.
AI eval register
Models, prompts, datasets, baselines, thresholds, metrics, traces, and failure patterns captured while fresh.
Time and finance ledgers
People, contractors, cloud, model API, grants, assets, and locations mapped to source documents.
Final review binder
An advisor-facing index of approved facts, draft narratives, evidence, costs, privacy status, and open questions.
Useful evidence support, not tax advice
This operating system helps a startup preserve what happened and prepare materials for qualified review.
It does not decide final eligibility, calculate a credit, promise a refund, file a claim, or replace a CPA or SR&ED specialist.
Technical leadApproves technical facts and experiment conclusions.
Finance ownerApproves source financial records and effort inputs.
Privacy ownerApproves redaction, export, and customer evidence handling.
AdvisorReviews SR&ED treatment, forms, expenditures, and open questions.
Company officerApproves external handoff and final company positions.
Open source ยท MIT
Start preserving evidence before the context disappears
Clone the toolkit, run the 14-day setup, and hand your advisor a binder built from approved facts.