Skip to content
Back to Paths

How It All Connects

Trace how a single thought becomes strategy through every Foundry surface

WorkflowWorkflow~12 min|3 checkpoints
Sign in to track progress

By the end of this module

Traced one idea from capture to weekly review
Created a relationship between two objects
Visited every surface an object touches

How a Thought Moves Through the System

Foundry's power is not in any single feature, it's in how objects move through the system and accumulate context as they go. A raw thought captured in 10 seconds can become a scored opportunity, a funded project, a logged decision, a reusable asset, and a lesson in your weekly review.

This module traces that full path so you can see how every surface relates to every other.

Insight:Most productivity tools are collections of independent features. Foundry is a pipeline. The value compounds because each stage adds context the next stage uses.

Stage 1: Capture → Vault

You're on a call and hear something interesting. You press Cmd+Shift+K (global capture shortcut) and type: "Competitor just dropped their enterprise tier — opportunity to position as the affordable alternative."

What happens:

  • A new Idea is created at RAW status

  • It appears in your Vault (the idea library)

  • It appears in Today as a stale capture if you don't process it within 7 days

  • The Recommendations engine starts watching: if you tag it and the tag appears on 3+ other ideas, it will suggest RECURRING_THEME


Surfaces touched: Capture, Vault, Today (after 7 days), Recommendations (if tagged)

Stage 2: Triage → Opportunity

A few days later, your triage queue has 6 items. You open Triage and start scoring.

For your competitor idea, you score all 16 criteria. The system computes a weighted score of 72/100 and suggests EXPLORE_ACTIVELY. You agree and assign that outcome.

What happens:

  • The idea moves from RAW → IN_TRIAGE → CLASSIFIED

  • An OpportunityScore record is created with all 16 scores

  • The outcome label (EXPLORE_ACTIVELY) is attached

  • If you have the Pro plan, you could have clicked AI Score to get AI-suggested scores first, then adjusted


Surfaces touched: Triage (scoring panel), Vault (status changes), Recommendations (may trigger CONVERT_TO_ASSET if score is high)

Stage 3: Decision → Project

The scored opportunity sits in your vault. During your next weekly review, you see it in the "High-potential ideas" section. You decide to act on it.

You go to Decisions → New Decision and log: "Decided to reposition product as the affordable enterprise alternative." You fill in reasoning, alternatives considered, assumptions, and what would prove you wrong. You set a revisit date 30 days out.

Then you go to Projects and create a new project: "Enterprise Repositioning." You link it to the decision. You set the energy type to COMPOUNDING.

What happens:

  • A DecisionLog record is created with full context

  • The decision appears in Today when its revisit date arrives

  • A new Project is created (capacity-checked against your Focus limit)

  • A LinkRelation connects the decision to the project

  • The project appears on the Focus page with energy classification

  • The project appears on the Architecture diagram


Surfaces touched: Decisions, Projects, Focus, Today (at revisit), Relationships, Architecture Diagram

Stage 4: Execution → Commitments → Journal

You start working on the repositioning. You promise your advisor: "I'll send you the revised positioning doc by Thursday." You log this as a Commitment linked to the project.

As you work, you write journal entries on the project detail page: progress notes, blockers, small wins. These feed the project's health score.

What happens:

  • The Commitment appears on Today and the Commitments page

  • It's filterable by person (your advisor) before your next call

  • Journal entries increase the project's health score

  • The Focus page shows this project's sub-projects (if any) with purple connector lines

  • Any linked projects show in yellow on the Focus card


Surfaces touched: Commitments, Today, Project Detail (journal), Focus (health + links)

Stage 5: Asset Conversion

During the repositioning work, you develop a pricing comparison framework that's genuinely reusable. You go back to the original idea in the Vault and click Convert to Asset.

You set the asset type to BUSINESS_FRAMEWORK, mark it as reusable, and link it to the project.

What happens:

  • The idea status changes to CONVERTED

  • A new Asset record is created in the Vault

  • The asset is linked to the source idea and the project

  • The Recommendations engine may suggest this asset for other projects via CONVERT_TO_ASSET recommendations


Surfaces touched: Vault (conversion), Project Detail (linked assets), Recommendations

Tip:Assets are the compounding output of your work. Every project should produce at least one reusable asset — a framework, a lesson learned, a decision pattern, a template. If a project closes with zero assets, you captured no durable value.

Stage 6: Weekly Review → Reflection

Sunday. You open Weekly Review and go through the 5-step ritual:

1. Commitments — your advisor commitment is done, you check it off
2. Reflect — you write a short reflection on the week
3. Clear Queue — you park 2 stale captures
4. Wins & Learnings — you log the pricing framework as a win, save it as a learning asset
5. Intentions — you set 3 intentions for next week

If you're on Pro, you click AI Summary and get: "Strong week. Top win: pricing framework created. Biggest risk: no customer validation on the new positioning yet. Suggested focus: schedule 3 customer calls before committing further."

What happens:

  • A WeeklyFocusSnapshot is saved

  • Your intentions appear on Today for the next 7 days

  • The learning asset goes to the Vault

  • The AI summary (if used) gives you a strategic second opinion

  • The Focus page's "This Week's Focus" section updates


Surfaces touched: Review, Today (intentions), Vault (learning asset), Focus (snapshot)

Stage 7: Revisit → Loop Closes

30 days later. The decision revisit appears on Today: "Revisit: Reposition as affordable enterprise alternative."

You open the decision. You read your original reasoning, assumptions, and what-would-prove-wrong conditions. You look at the evidence from 30 days of execution.

You record the verdict: VALIDATED — the repositioning is working, early customer feedback is positive.

What happens:

  • The decision status changes to VALIDATED

  • The revisit is cleared from Today

  • The decision remains in your permanent log as a reference

  • If you'd chosen PROVED_WRONG, you'd create a new decision (the replacement) and mark this one SUPERSEDED, with a REPLACES relationship linking them


The loop is complete. A 10-second capture became: a scored opportunity → a strategic decision → a capacity-governed project → tracked commitments → a reusable asset → a weekly reflection → a validated decision. Every stage added context. Nothing was lost.

Insight:This is the full operating loop. Most founders run pieces of it informally — capturing ideas here, making decisions there, reviewing occasionally. Foundry makes the loop explicit, structured, and permanent. The value is not in any single step but in the fact that context accumulates and nothing falls through the cracks.

The Object Relationship Map

Every object in Foundry can connect to others:






ObjectCan link toVia
------------------------
IdeaProjects, Assets, Decisions, other IdeasTags, Relationships, projectId
AssetProjects, source IdeasourceIdeaId, projectId, Relationships
DecisionProjects, Ideas, Assets, other DecisionsRelationships, projectId
CommitmentProjectsprojectId
ProjectParent/child Projects, all aboveparentId, Relationships

Relationships page is where you create explicit links (SUPPORTS, DERIVED_FROM, REUSABLE_FOR, AFFECTS, etc.). Tags create implicit groupings. projectId scopes objects to a project.

The Architecture Diagram visualizes project-to-project relationships as a network. Yellow curved lines are cross-project links. Purple lines are parent-child hierarchies.

When you're unsure how two things relate, create a Relationship. When you revisit it later, the link will remind you why you connected them.

Practice Checkpoints

Traced one idea from capture to weekly review
Created a relationship between two objects
Visited every surface an object touches

Sign in to track your progress and mark checkpoints complete.

Next in Foundations Path

Working With Foundry's AI

9 AI features, finite monthly budgets, and a clear rule for which to use when.

Start module

workflow

Workflow Path

Read time
~12 min
Checkpoints
3 items

Sign in to track

Sections
9 sections

In this module

How a Thought Moves Through the SystemStage 1: Capture → VaultStage 2: Triage → OpportunityStage 3: Decision → ProjectStage 4: Execution → Commitments → JournalStage 5: Asset ConversionStage 6: Weekly Review → ReflectionStage 7: Revisit → Loop ClosesThe Object Relationship Map