Change it once.
Everything follows.

North traces what a decision affects, then keeps every person, artifact, product, and agent working from the same Direction.

Open North →Try the playground ↓
Not find-and-replace

North understands the project — not just the string you changed.

Moving a deadline is never only a date. Scope may change. The development plan may slip. Tickets go stale. The deck and website can keep saying the old month. North finds what is impacted and proposes the updates.

ExampleLaunch moves August → OctoberOne approved Direction change
  1. Scope & milestonesWhat still fits the new window — and what gets cut
  2. Development planSequencing, capacity, and what ships before launch
  3. TicketsDue dates, remaining work, and owners
  4. Investor deckStill says August — outbound claims go stale
  5. WebsitePublic launch date and related copy

North identifies the stale and impacted work, then proposes a coordinated update — you approve what actually moves.

A simple example

Here’s a small version you can try.

Change the approved plan — then watch website, Jira, and deck catch up one by one.

Project planClick to edit
Project planApproved
Edit the approved planClick any field. Connected work updates automatically.
New evidence

Security review remains incomplete.

North suggests

Keep August as the private beta and move the public launch to October?

Milestones1/2 done
Connected workLive preview · read only
Synced
https://northwind.com
Northwind
ProductPricingDocs
Get started
Launching August 2026
Ship a project that never goes stale.

One decision. Every page stays true.

Start free →
PROJ-142

Ship Northwind public launch

Due dateAugust 2026
PriorityHigh
PROJ-140Onboard design partnersDone
PROJ-141Complete security reviewTo Do
Pitch deck
Series A
Northwind
Ship a project that never goes stale.
Public launch
August 2026

Scripted demo — a fixed path so anyone can feel the loop without burning AI credits. Real North reasons over project history and proposes changes with AI.

How North thinks

North turns change into coordinated action.

What happened informs what the team decides. Those decisions reach the documents, products, people, and agents that depend on them.

1Evidence
What happened

Meetings, emails, research, customer feedback, metrics, and commits form a durable trail of what changed.

2Decisions
What the organization believes now

Approved decisions, goals, assumptions, constraints, and open questions the team is working from.

3Action
Where work takes effect

Documents, websites, tickets, products, people, and agents get the context they need to stay aligned.

  1. Detect evidence
  2. Propose a change
  3. See what depends
  4. Prepare updates
  5. Human approves
How North finds dependencies

North reads the project, then draws the map.

It classifies every artifact, finds Direction anchors, and only connects relationships the evidence can support.

  1. 1Scan the project

    North reads the Drive folder, docs, decks, tickets, and linked surfaces in scope.

  2. 2Classify each artifact

    Record, Direction, or Living — plus whether it is authoritative or dependent.

  3. 3Infer relationships

    informs · implements · communicates · tracks — only when evidence backs the edge.

Project graph · 6 nodes · evidence-backed
DIRECTION ANCHORLaunch · October
Launch planinforms · Decision docCurrent
Investor deckcommunicates · still says AugustConflict
Websiteimplements · public copyNeeds update
Jira epictracks · launch workNeeds update
Codex jobimplements · pricing pageContext ready

Change Direction once — North already knows the blast radius.

Investor deck still says August
The larger idea

North does more than keep work aligned.

It builds the shared understanding that lets people and agents ask, act, and verify with the full project behind them.

Alignfrom the playground

Keep every surface working from current Direction.

Ask

Answer with project context and supporting evidence.

Act

Package project context and start jobs in specialized agents.

Verify

Catch problems before work is published, merged, or shipped.

North is not another agent. It is the shared context behind every person, tool, and agent.

Trust and control

AI can propose. Your team stays in control.

Every change includes its evidence, reasoning, dependencies, proposed edits, and an audit trail. Review, edit, approve, reject, or undo before anything moves.

Diff inboxProposed
August→October

Affects 5 living documents

ApproveReject

Diff inbox

Proposed changes land here — with source, confidence, and blast radius before anything moves.

⇣
⇡
⇣ Pull latest⇡ Push change

Evidence & control

Pull stale docs up to date or push a change outward — always with a receipt and a path to undo.

Pitch deckQueued
Jira ticketQueued
WebsiteQueued

Blast radius

See which surfaces will update — then write natively in each tool, formatting preserved, every edit logged.

Works in your existing tools

Your tools. One shared Direction.

North works where the project already lives.

Google DocsSlidesJiraGitHubNotionWebsite

Move fast without losing the plot.

North gives every person, artifact, product, and agent the context needed to act from the same evolving understanding.

Open North →