FOUNDER OS · MAJOR WAVE 16 · DECISION OUTCOME RECEIPT + RECHECK
Finish the mission. Recheck the decision before you carry it forward.
Pick one company, complete one evidence-producing mission, review what happened, then confirm the decision is still supported by current evidence before carrying the next move forward. The existing mission engine, Company Memory, Decision Log and device storage remain the source of truth.
Wave 16 strengthens decision outcome receipts and recheck safety using the existing outcome controls, Decision Log, Company Memory and Decision Expiry Review. Every material decision should retain its named human owner, decision date, evidence basis, expected signal and explicit re-review trigger. When customer, market, financial or operating evidence changes, record the observed outcome and choose keep, revise or reopen instead of silently carrying stale evidence forward. Unknown outcomes stay unknown and must not be presented as success. Existing mission history, device storage, SD1 session and completion-return behavior remain unchanged. No new storage schema, account, billing, backend or synchronization claim is added.
FOUNDER OS · MAJOR WAVE 8
One founder. Multiple companies. Never mix the evidence.
Choose the company or project before a mission, decision or mentor brief. Wave 8 adds the workspace boundary without creating a new storage schema or changing the SD1 completion-return contract.
1 · NAME ITUse Company Memory to identify the active company/project.
2 · KEEP PROOF TOGETHERMission evidence and decisions stay tied to the selected context.
3 · BACK UP BEFORE SWITCHINGUse the existing Full Backup before moving between company workspaces.
Boundary rule: never assume two company/project names share authority, evidence, decisions or customer context. No account sync or live multi-tenant backend is claimed.
FOUNDER OS · MAJOR WAVE 6
Move the opportunity. Record the proof. Make the commercial decision.
A tighter commercial review that connects the existing pipeline, mission evidence and Decision Log without adding another data store.
Unknown stays unknown. Wave 6 adds no storage key, schema/backend call, billing behavior, account claim, or SD1 completion-return change.
FOUNDER OS · MAJOR WAVE 7 · SIMPLIFIED WORKSPACE
Core workspace first. Older tools stay available only when you need them.
Mission, evidence, Company Memory and commercial review remain the primary path. Historical v1.x panels are collapsed below without deleting their data or controls.
Open advanced / historical tools
Use the deeper decision, mentor, evidence-reuse and legacy workspace panels below when a specific review requires them.
FOUNDER OS · MAJOR WAVE 2
Know the next move. Do it. Prove it.
One founder command deck for missions, evidence, decisions and the exact Skill you need. The deeper tools remain below when you need them.
Major Wave 2 adds no new browser storage and changes no existing mission/SD1 return contract.
DECISION CLOSURE LOOP • v1.61
A decision is not finished until its result comes back into Company Memory.
After an important choice, schedule the evidence that will tell you whether the decision worked, needs adjustment, or should be reversed.
Decision made
Record the choice, date and why it was made.
Expected signal
Define the customer, revenue, product or operating evidence expected next.
Review date
Set when the outcome should be reviewed instead of leaving it open-ended.
Feed back
Update the Decision Log, Company Memory and next mission using the observed result.
No new browser-storage key is introduced. Existing Decision Log, Company Memory, Mission Brief, Memory Intelligence and the v1.39 SD1 completion-return contract remain unchanged.
EVIDENCE REUSE MAP • v1.62
One useful piece of evidence should strengthen more than one founder decision.
Before collecting more data, check whether existing mission evidence already belongs in the Decision Log, Company Memory, mentor brief or next mission.
Mission evidence
Start with the observable result already captured.
Decision impact
Identify which assumption, decision or opportunity the evidence changes.
Portable brief
Reuse the same fact in a mentor, investor or partner brief instead of rewriting it from memory.
Next mission
Turn the unresolved implication into the next focused test.
This release introduces no new browser-storage key and does not change the v1.39 SD1 completion-return contract.
DECISION CONFIDENCE CHECK • v1.63
Make confidence explicit before a founder commits resources.
Use a simple confidence check to separate evidence-backed conviction from urgency, optimism or incomplete information.
Evidence strength
Rate whether the decision rests on direct evidence, indirect signals or mostly assumptions.
Downside
State the cost of being wrong in money, time, customer trust or strategic delay.
Confidence band
Use low, medium or high confidence instead of false numerical precision.
Next evidence
Name the smallest new signal that would materially change the decision.
No new browser-storage key is introduced. Existing Decision Log, Company Memory, Mission Brief, Memory Intelligence and the v1.39 SD1 completion-return contract remain unchanged.
DECISION REVIEW GATE • v1.60
Before a major decision, prove that the choice is ready to be made.
Use this lightweight review before pricing, hiring, product, partner, fundraising, or go-to-market decisions. It keeps urgency from outrunning evidence.
Decision
State the exact choice and the alternatives still available.
Evidence
Name the strongest observable facts supporting the choice and what remains uncertain.
Reversibility
Classify the decision as easy to reverse, costly to reverse, or effectively one-way.
Trigger
Define the next signal or date that would confirm, revise, or reverse the decision.
No new browser-storage key is introduced. Use the existing Decision Log, Company Memory, Mission Brief, and Memory Intelligence Decision Brief. The v1.39 SD1 completion-return contract is unchanged.
MENTOR READINESS • v1.59
Walk into a mentor, investor, or advisor conversation with evidence instead of a status dump.
Before sharing a Founder OS brief, make sure the conversation can answer four things: what changed, what evidence exists, what decision is unresolved, and what specific help is needed next.
1. Context
Company focus, active mission, and the important change since the last review.
2. Evidence
Observable customer, commercial, product, financial, or operational signal.
3. Decision
The unresolved choice, assumption, or tradeoff that actually needs judgment.
4. Ask
One explicit request: challenge the assumption, make an introduction, review a decision, or test a plan.
Use the existing Mission Brief and Memory Intelligence Decision Brief as the portable handoff. This release adds no new storage key and does not change the v1.39 SD1 completion-return contract.
COMMERCIAL PIPELINE • v1.57
Turn founder conversations into a decision-ready pipeline.
Keep opportunity stage, commercial value, next action and decision date connected so promising conversations do not disappear into notes.
Stage
Signal, discovery, proposal, negotiation, won, lost or parked.
Commercial value
Record a realistic range and confidence instead of treating every conversation as equal.
Next action
Name the smallest concrete follow-up, its owner and the evidence expected.
Decision date
Set when to follow up, close, continue or stop pursuing the opportunity.
DECISION EXPIRY REVIEW • v1.64
A good decision can become stale when the evidence changes.
Review important decisions when their assumptions, market conditions, customer evidence or operating constraints have materially changed.
Original basis
State the evidence and assumptions that supported the decision when it was made.
What changed
Identify the new customer, commercial, product, financial or operating signal.
Still valid?
Choose keep, revise or reopen instead of silently carrying an old decision forward.
Next review
Set the next trigger or review date only when the decision remains material.
No new browser-storage key is introduced. Existing Decision Log, Company Memory, Mission Brief, Memory Intelligence and the v1.39 SD1 completion-return contract remain unchanged.
✦
Founder OS
SD1 · FOUNDER TRACK · MISSION · EVIDENCE
● v1.64 LIVE● DEVICE SAVE ACTIVEACCOUNT: NOT VERIFIED
POWERED BY SKILL DESK ONE · SD1
Founders is the entrepreneur track. Founder OS is its private mission workspace.
Skill session ready. Open the selected Skill in a new tab; Founder OS will notice when you return.
Skill proof: waiting.
REAL STATUS
0
completed missions on this device
Origin active
FOUNDER OS PRO · PREVIEW
Monetize continuity.
Planned Pro value: account sync, longer evidence history, multiple companies, AI Guide continuity and account-synced briefs.
Not live billing yet — product/price test only.
RECENT COMPLETIONS · DEVICE ONLY
Your last completed missions
Keeps up to 5 locally.
No completed missions yet.
COMPANY MEMORY · v1.42 · PORTABLE · DEVICE ONLY
Keep the decisions, not just the tasks.
A portable workspace memory for company focus, decisions, completed missions, evidence and Skill-proof source. Back it up, move it, or restore it without uploading anything automatically.
0 records
Build your first Company Memory snapshot.
DECISION LOG · v1.41
No decisions recorded yet.
PORTABLE WORKSPACE · v1.58
Full backup includes the company profile, active mission, recent mission history and decision log. Import creates a local safety snapshot before replacing recognized SD1 workspace fields.
MEMORY INTELLIGENCE · v1.42 · LOCAL DECISION ENGINE
What should I do next?
Uses your current focus, Decision Log, active mission, checklist state, evidence and recent completed work. This is transparent local logic — not server AI.
Context strength: 0/4
SIGNAL
Waiting for company memory.
RISK
Waiting for context.
NEXT MOVE
Build the recommendation when you are ready.
SD1 SESSION HEALTH · v1.43
Know whether the Skill handoff actually worked.
This reads only browser-local mission/session state. It does not upload evidence, company memory, or private notes.
CarrySkills v3.9.3 remains the known-good browse engine. The mission-specific browser bridge is handled by /skills-session/.
EVIDENCE QUALITY · v1.45
Record evidence that can change the next decision.
Strong mission evidence should describe an observable result, not just that the task was completed.
Response
Reply, meeting booked, objection, acceptance, rejection or silence.
Number
Price tested, conversion, cost, runway, clicks or another measurable signal.
Exact language
Capture the buyer or user’s wording when it affects positioning or product decisions.
Next decision
State what the evidence makes you do next, including when the result is “do nothing yet.”
EVIDENCE SCORECARD · v1.46
Before you close a mission, check whether the evidence is actually useful.
Observable?
Could another person verify that something happened?
Specific?
Does it include a number, quote, date, response or concrete outcome?
Decision-ready?
Does the evidence clearly change, confirm or delay the next move?
Reusable?
Would this still help you understand the company a month from now?
MISSION EXIT CRITERIA · v1.47
Do not close a mission just because the checklist is green.
Use the evidence to choose one of three explicit outcomes so the work changes the company instead of becoming busywork.
Close
The objective was met and the next move is clear.
Continue
The signal is promising but more evidence is required before deciding.
Pivot
The evidence contradicts the assumption; change the offer, audience, price or mission.
OUTCOME → NEXT ACTION • v1.49
Do not leave a completed mission without an owner and a date.
After choosing Close, Continue or Pivot, capture the smallest next action that follows from the evidence.
Owner
Who is responsible for the next move?
Action
What is the smallest concrete next step?
By when
Set a real decision or follow-up date.
Success signal
State what observable evidence will tell you the action worked.
FOLLOW-THROUGH QUEUE • v1.50
Turn next actions into a visible operating queue.
After a mission closes, keep the owner, due date and success signal visible until the real-world follow-up is complete.
Due now
Actions whose target date has arrived and still need evidence.
Waiting
Buyer, partner, candidate or customer responses that have not resolved yet.
Decision date
A date when silence or incomplete evidence becomes a decision signal.
Close loop
Record the result back into Company Memory so the same issue is not rediscovered later.
CUSTOMER SIGNAL REGISTER • v1.54
Separate repeated market signal from one-off noise.
Capture recurring objections, requests, buying language and willingness-to-pay evidence so the same market lesson is not rediscovered across missions.
Signal
What exact behavior, objection, request or phrase keeps appearing?
Frequency
How many independent customers or buyers produced the same pattern?
Commercial weight
Did it affect price, conversion, retention, urgency or a real purchase decision?
Next test
Turn material signals into a mission instead of changing strategy from anecdotes.
EXPERIMENT LEDGER • v1.55
Keep hypothesis, test, result and decision connected.
A founder should be able to see what was believed, what was actually tested, what happened and what changed next without reconstructing the story from scattered missions.
Hypothesis
State the belief in a form that could be disproved.
Test
Link the smallest mission or customer action that tests it.
Result
Record observable evidence, including negative or inconclusive outcomes.
Decision
Close, continue or pivot with the evidence preserved for later review.
REVIEW RHYTHM • v1.53
Give decisions a date before they become drift.
Use a lightweight review cadence so assumptions, follow-through items and unresolved decisions return to attention at the right time.
Daily
Only overdue actions and blockers that can change today.
Weekly
Review follow-through, waiting responses and evidence gaps.
Monthly
Revisit material assumptions, pricing, runway and strategic choices.
Escalate
Turn any unresolved material item into a mission with evidence and an owner.
ASSUMPTION WATCHLIST • v1.52 • DEVICE LOCAL
Keep fragile assumptions visible until evidence settles them.
Capture a testable belief, the evidence needed, and the date it must be revisited. Escalate a watch item into a real Founder OS mission when it becomes material.
0 watched
No assumptions watched yet.
KPI PULSE • v1.56 • DEVICE LOCAL
Track the few numbers that should change a founder decision.
Keep up to eight key performance indicators (KPIs) with a current value, target and review date. Overdue or off-target metrics stay visible without pretending to be server analytics.
0 metrics
No KPIs tracked yet.
Factual status: device mission persistence, skill-review state, evidence notes, local completion history, portable Company Memory, the Decision Log, v1.42 local Memory Intelligence, the Mission Brief, v1.43 SD1 Session Health, the SD1 Mission Session producer, and the verified completion-return consumer are live. Browser-level automatic proof now returns from the SD1 Mission Session only when mission, Skill, completion status and one-time nonce match. The full /skills/ plugin library is still a separate browse engine. Account/server verification is not live. RelayDesk and BrightWatcher are not wired into this loop.
