Your First Week

You're connected. Now what? This guide walks you from a blank workspace to one that's genuinely useful — with concrete actions for each day.

Before you start: Complete the Quickstart so your MCP connection is working and momental_whoami() returns your identity.

Day 1 — Anchor the workspace

A Momental workspace without a mission and vision answers every question generically. The first thing to do is give it a strategic frame.

1. Set mission and vision

In the workspace UI: Strategy → New Node → VISION. One sentence. Then add a MISSION node as its child.

const vision = await momental_strategy_create({
  nodeType: "VISION",
  statement: "Every company knows what it believes"
});
// parentId links mission to vision
await momental_strategy_create({
  nodeType: "MISSION",
  statement: "Build the alignment platform for product teams",
  parentId: vision.id
});

2. Create 3 atoms from memory

Pick 3 decisions your team has made in the last 90 days — things that would confuse a new hire if they weren't written down. Create one atom for each:

await momental_node_create({
  statement: "We do not support IE11 - drop it without a shim",
  nodeType: "DECISION",
  status: "ACTIVE",
  domain: "engineering"
});

Don't overthink the wording. Done is better than perfect. You can edit atoms later.

3. Ask Huginn something

Open the workspace chat and ask: "What do we know about our pricing strategy?" Huginn will return what it found — probably just your new atoms. That's fine. The answer will improve as you add more.

Notice that Huginn cites each atom it retrieved. That citation is the core value: answers grounded in your actual decisions, not the model's general knowledge.

Day 3 — Go deeper

4. Upload a document

Find a design doc, retrospective, or meeting notes file. Upload it — Momental extracts atoms automatically. A 10-page doc typically yields 15-30 atoms in a couple of minutes.

In the UI: Knowledge → Upload Document. Then review the extracted atoms and publish the ones that are accurate. This is the fastest way to get a rich knowledge graph without typing everything manually.

5. Create your first OKR

Add a current objective to the strategy tree. Link it to your mission node. This gives Huginn and the agents the context they need to understand what you're working toward.

const objective = await momental_strategy_create({
  nodeType: "OBJECTIVE",
  statement: "Reach 1,000 paying teams by end of Q3",
  parentId: "node_mission_id"
});

6. Link atoms to strategy

Go back to the atoms you created on day 1. Link each one to the most relevant strategy node. In the UI: open an atom, click Link to Strategy. Linked atoms appear as evidence in strategy node views — useful when reviewing whether your current decisions still support your goals.

Day 7 — First agents

7. Assign Huginn a review task

Create a task and assign it to Huginn. A good first task: ask it to review your knowledge graph for conflicts or outdated decisions.

const task = await momental_task_create({
  statement: "Review engineering decisions for gaps and conflicts",
  parentId: "node_objective_id",
  acceptanceCriteria: "List stale or conflicting decisions"
});
// Assign the task to Huginn
await momental_task_assign_agent({
  taskId: task.id,
  agentId: "huginn"
});

Huginn picks up within a few minutes and posts findings to the task thread.

8. Connect Heimdall (if you have a GitHub repo)

Go to Settings → Apps → Heimdall, subscribe ($49/mo), and install the GitHub App on your org. Open any PR — Heimdall posts a review comment automatically. See Heimdall: Your First PR Review for what to expect.

9. Resolve your first conflict

By now Momental has probably flagged a conflict — two atoms that say contradictory things, or an atom that contradicts your strategy. Check Knowledge → Conflicts in the UI. See Resolve a Conflict for how to handle it.

Day 30 — What a healthy workspace looks like

After a month of consistent use, a healthy Momental workspace has:

Call momental_my_activity() to see a summary of what's been built.

Common mistakes in the first week

MistakeFix
Creating atoms in DRAFT status Always set status: "ACTIVE" — DRAFT atoms are invisible to agents
Writing atoms too broadly "We value quality" is useless. "We don't ship without a passing test suite" is actionable.
Skipping atom review after document upload Extracted atoms are DRAFT until you publish them. Review takes 2 minutes.
Not linking atoms to strategy Unlinked atoms float. Link them and they become evidence in strategy views.
Treating it like a chatbot The more you put in, the better answers get. Ask Huginn to surface what it knows, then fill the gaps.