Evidence
“We agreed CS should own rollout now that the product build is complete.”
Team thread #ops · 10:24 AM
Source control for
company decisions
Process CI detects decisions in team conversations, drafts the change, attaches the evidence, and routes it to the right people for review.
Proposal #149 – Customer onboarding
Clarify onboarding ownership
- Product owns onboarding rollout
+ Customer Success owns onboarding rollout
+ Product owns activation UX
Reviewers
- Maya Chenapproved
- J. Okaforpending
- D. Rourkepending
Capture
Decisions start in team conversations.
Ownership, process, and policy change long before the docs catch up.
Extract
Turn conversations into proposed changes.
Process CI extracts what changed, why it matters, and where the evidence came from.
Extracted proposals
Ready for review
- Customer Success owns onboarding rollout.Source: Team thread #ops · 10:24 AMReady
- High-value order edits require ownership verification.Source: Team thread #support · yesterdayReady
- EU refund exception was approved.Source: Team thread #refunds · yesterdayReady
- Weekly ops sync retires after Friday.Source: Team thread #operations · 2d agoReady
Review
Approve before it's recorded.
Review the diff, source, evidence, and owner before company memory updates.
Proposed change
Clarify onboarding ownership
- Product owns customer onboarding.
+ Customer Success owns onboarding rollout.
+ Product owns activation UX.
Evidence
- Team thread #ops · 10:24 AM
- Team thread #support · yesterday
- Team thread #operations · 2d ago
Reviewers
- Maya Chenapproved
- J. Okaforpending
- D. Rourkepending
Features
Every decision stays traceable.
See the diff, evidence, approver, owner, and history behind every accepted change.
See what changed. Not just what was decided.
See exactly what changed before a proposal is approved.
Statement diff
3 changes−Product owns onboarding flow
−Sales runs all first-call demos
+Engineering owns onboarding flow
+Customer Success joins enterprise trials from call two
+Andy owns billing rewrite until June
Every change links back to the conversation.
Every proposal links back to the source conversation it came from.
#leadershipWho owns onboarding after the reorg?10:24 AM- #engineeringAndy billing rewrite — scope through JuneYesterday
- #gtmEnterprise trial handoff from Sales to CSYesterday
Keep the right people in the review.
Route each change to the people who need context before it updates company memory.
ReviewersStatus
- Sofia ReyesCEOApproved10:32 AM
- Andy KimVP EngineeringApproved11:04 AM
- Jordan LeeHead of CSPendingYesterday
Go back to any point in company history.
See what was true then, who approved it, and what changed since.
Company memory
- TodayCS owns onboarding rolloutCurrent
- May 14Product owns activation UXApproved
- Apr 02Sales owns first-call demosArchived
For teams where context loss creates risk.
Founders
Stop being the person everyone asks when the company forgets why something changed.
Operators
Keep process updates reviewable without maintaining another wiki.
Team leads
Preserve decisions through handoffs, onboarding, and reorgs.
Stop losing the reasons behind decisions.
Join the private preview and build a reviewed history of how your company actually works.
Join private preview