qwen-base 1.0.0

package/src/commands/orientation/tasks/north-star.md

@@ -0,0 +1,97 @@
+<purpose>
+Define the operator's North Star — the one key metric or outcome that everything else aligns toward. Derives from the Deep Why and gives initiatives a measurable target.
+</purpose>
+
+<user-story>
+As an operator, I want a single guiding metric that tells me whether my work is pointing in the right direction, so that I can evaluate opportunities and say no to misaligned ones.
+</user-story>
+
+<when-to-use>
+- Phase 2 of new orientation (after Deep Why)
+- Operator chose to reorient their North Star specifically
+- Composed by new-orientation.md or reorientation.md
+</when-to-use>
+
+<steps>
+
+<step name="ground_in_deep_why" priority="first">
+<if condition="previous orientation exists">
+> Your previous North Star was:
+> *"{previous metric}" ({previous timeframe})*
+</if>
+
+> Your Deep Why: *"{deep_why_statement}"*
+>
+> A North Star is the one metric or outcome that, if you achieved it, would mean your Deep Why is being lived. It's not a task. It's not a project. It's the thing that makes all the projects make sense.
+>
+> What's the one outcome that matters most to you right now? Think in terms of something you could measure or clearly evaluate.
+
+**Wait for response.**
+</step>
+
+<step name="refine_metric">
+Evaluate the response:
+
+- If too vague ("be successful", "make an impact"): Push for specificity. "What would you point to as proof that's happening?"
+- If too narrow ("launch CaseGate"): Push for altitude. "That's a project, not a star. What does completing that project serve?"
+- If it's a feeling ("feel free"): Acknowledge it, then ask "What would be true in your life when you feel that? What's the measurable version?"
+
+Once the metric is crisp:
+
+> **Your North Star metric:**
+> *"{metric}"*
+>
+> What timeframe feels right for this? Not a deadline — a horizon. When would you evaluate whether you're on track?
+>
+> **[1] 6 months**
+> **[2] 1 year**
+> **[3] 2-3 years**
+> **[4] Custom — I'll specify**
+
+**Wait for response.**
+</step>
+
+<step name="rationale">
+> Last piece — why this metric above all the others you could have chosen? One sentence.
+
+**Wait for response.**
+</step>
+
+<step name="confirm_and_lock">
+> **Your North Star:**
+> *"{metric}"*
+> **Timeframe:** {timeframe}
+> **Why this one:** {rationale}
+>
+> **[1] Lock it in**
+> **[2] Adjust the metric**
+> **[3] Adjust the timeframe**
+
+**Wait for response.**
+</step>
+
+<step name="lock">
+North Star is locked.
+
+Return to parent workflow with:
+- `metric`: the north star metric
+- `timeframe`: chosen horizon
+- `rationale`: why this metric
+- `completed_at`: current ISO date
+
+This phase is complete. Parent workflow resumes.
+</step>
+
+</steps>
+
+<output>
+North Star data: metric + timeframe + rationale, ready for operator.json.
+</output>
+
+<acceptance-criteria>
+- [ ] Metric is specific and evaluable (not vague aspiration)
+- [ ] Metric connects back to Deep Why
+- [ ] Timeframe is set
+- [ ] Rationale captured
+- [ ] Operator approved the final North Star
+</acceptance-criteria>

package/src/commands/orientation/tasks/project-mapping.md

@@ -0,0 +1,103 @@
+<purpose>
+Map existing projects to their parent initiatives and sync PAUL satellite data. Every project should trace to an initiative or be explicitly unparented.
+</purpose>
+
+<user-story>
+As an operator with defined initiatives, I want my projects organized under the right strategic objectives with current PAUL data, so that I can see which work serves which goal.
+</user-story>
+
+<when-to-use>
+- Phase 7 of new orientation (after Initiatives)
+- Operator wants to reorganize project-to-initiative mappings
+- Composed by new-orientation.md or reorientation.md
+</when-to-use>
+
+<steps>
+
+<step name="pull_current_state" priority="first">
+Pull initiatives and projects in parallel:
+- base_list_projects(type="initiative")
+- base_list_projects(type="project")
+
+Display initiatives as target buckets, then list all projects with their current parent_id (or "unparented").
+
+> ## Initiatives (target buckets)
+> {For each: ID, title}
+>
+> ## Projects to Map
+> {For each: ID, title, current parent, status, PAUL satellite if any}
+>
+> I'll go through each project. Tell me which initiative it belongs under, or say "none" to leave it unparented.
+</step>
+
+<step name="iterate_projects">
+For each project without a parent (or with a stale/wrong parent):
+
+> **{PRJ-ID}: {title}** ({status})
+> {PAUL: satellite_name, phase if applicable}
+>
+> Which initiative does this serve?
+> {List initiative options as [N] brackets}
+> **[N+1] None — leave unparented**
+> **[N+2] Archive — no longer active**
+
+**Wait for response before moving to next project.**
+
+When assigned, update via base_update_project(id, {parent_id: "INI-XXX"}).
+</step>
+
+<step name="sync_paul_data">
+For each project that has a PAUL satellite (paul.json exists in its location):
+
+1. Read the paul.json file from the project's location
+2. Update the project's paul field with current: satellite_name, location, milestone, phase, loop_position, handoff status and path
+3. Update via base_update_project
+
+Report: "{N} PAUL satellites synced"
+</step>
+
+<step name="confirm_and_lock">
+Display the final mapping:
+
+> ## Initiative → Project Mapping
+>
+> **{INI-001}: {title}**
+>   - {PRJ-XXX}: {title} (PAUL: {phase} | {status})
+>   - ...
+>
+> **{INI-002}: {title}**
+>   - ...
+>
+> **Unparented:**
+>   - {PRJ-XXX}: {title}
+>
+> **[1] Looks right — lock it in**
+> **[2] Move a project**
+
+**Wait for response.**
+</step>
+
+<step name="lock">
+Project mapping is locked.
+
+Return to parent workflow with:
+- `mapped_count`: number of projects assigned to initiatives
+- `unparented_count`: number left without a parent
+- `paul_synced`: number of PAUL satellites updated
+- `completed_at`: current ISO date
+
+This phase is complete. Parent workflow resumes.
+</step>
+
+</steps>
+
+<output>
+All projects mapped to initiatives via Apex MCP. PAUL satellite data synced from paul.json files.
+</output>
+
+<acceptance-criteria>
+- [ ] Every project reviewed — assigned to initiative, left unparented, or archived
+- [ ] Parent IDs set via base_update_project MCP
+- [ ] PAUL satellites synced from source paul.json files
+- [ ] Final mapping displayed and approved by operator
+</acceptance-criteria>

package/src/commands/orientation/tasks/reorientation.md

@@ -0,0 +1,96 @@
+<purpose>
+Guide an operator through reorientation when an existing operator.json is present. Iterates through each section, showing current values and prompting for keep/reset decisions before composing relevant phase tasks.
+</purpose>
+
+<user-story>
+As an operator who has been through orientation before, I want to selectively reset parts of my identity profile, so that my profile evolves with me without starting completely from scratch every time.
+</user-story>
+
+<when-to-use>
+- operator.json already exists
+- Operator chose [1] Full reorientation from entry point
+</when-to-use>
+
+<context>
+@../templates/operator-json.md
+</context>
+
+<steps>
+
+<step name="load_current_profile" priority="first">
+Read `.base/operator.json` and display the full current profile.
+
+> ## Current Operator Profile
+>
+> **Deep Why:** {current statement}
+> *(Last set: {date})*
+>
+> **North Star:** {current metric} ({timeframe})
+> *(Last set: {date})*
+>
+> **Values:** {v1}, {v2}, {v3}, {v4}, {v5}
+> *(Last set: {date})*
+>
+> **Elevator Pitch:** {current pitch}
+> *(Last set: {date})*
+>
+> **Surface Vision:** {current summary}
+> *(Last set: {date})*
+
+Then begin iterating through each section.
+</step>
+
+<step name="iterate_sections">
+For each section in order (Deep Why, North Star, Key Values, Elevator Pitch, Surface Vision, Initiatives, Project Mapping, Task Seeding):
+
+> **{Section Name}**
+> Current: {current value — one-line summary}
+> Last set: {date}
+>
+> **[1] Keep** — this still resonates
+> **[2] Reorient** — this needs work
+> **[3] Skip for now** — come back to it later
+
+**Wait for response before moving to next section.**
+
+If [2]: Load and execute the corresponding phase task (e.g., @deep-why.md for Deep Why, @initiatives.md for Initiatives, @project-mapping.md for Project Mapping, @task-seeding.md for Task Seeding), passing current value as "previous orientation" context so the operator can see what they had before. When phase task completes, capture new output and continue iteration.
+
+If [1] or [3]: Keep current value, move to next section.
+
+Track which sections were reoriented vs kept.
+</step>
+
+<step name="write_updated_profile">
+After iterating all 8 sections:
+
+1. Merge kept values with new values from reoriented sections
+2. Update `last_updated` timestamp
+3. Update `completed_at` only for sections that were reoriented
+4. Write updated `.base/operator.json`
+5. Display summary showing what changed:
+
+> ## Reorientation Complete
+>
+> **Changed:** {list of reoriented sections}
+> **Kept:** {list of kept sections}
+> **Skipped:** {list of skipped sections}
+>
+> Profile updated at `.base/operator.json`.
+
+**Wait for acknowledgment.**
+</step>
+
+</steps>
+
+<output>
+Updated `.base/operator.json` with selectively reoriented sections.
+</output>
+
+<acceptance-criteria>
+- [ ] Current profile loaded and displayed
+- [ ] Each section presented with keep/reorient/skip options
+- [ ] Reoriented sections went through their full phase task
+- [ ] Kept sections preserved unchanged
+- [ ] operator.json updated with merged results
+- [ ] Summary shows what changed vs what stayed
+</acceptance-criteria>

package/src/commands/orientation/tasks/surface-vision.md

@@ -0,0 +1,113 @@
+<purpose>
+Guide the operator to conjure 2-5 concrete, tangible future moments that represent what their life looks like when things are working. These are sensory anchors — specific enough to visualize, "superficial" on purpose because the surface is what the inner world connects to.
+</purpose>
+
+<user-story>
+As an operator, I want tangible anchor points for the future I'm building toward, so that my inner psychology has something concrete to orient around rather than abstract goals.
+</user-story>
+
+<when-to-use>
+- Phase 5 of new orientation (after Elevator Pitch)
+- Operator chose to reorient their Surface Vision specifically
+- Composed by new-orientation.md or reorientation.md
+</when-to-use>
+
+<steps>
+
+<step name="set_the_frame" priority="first">
+<if condition="previous orientation exists">
+> Your previous Surface Vision scenes:
+> - {scene 1}
+> - {scene 2}
+> - {scene 3}
+> Summary: *"{previous summary}"*
+</if>
+
+> Your foundation:
+> - **Deep Why:** {statement}
+> - **North Star:** {metric}
+> - **Values:** {v1}, {v2}, {v3}, {v4}, {v5}
+> - **Pitch:** {pitch}
+>
+> Surface Vision is different from the others. This isn't about metrics or statements. This is about moments.
+>
+> Close your eyes for a second. Picture your life when the North Star is hit and the Deep Why is being lived daily. Don't think about the business model or the revenue. Think about a single moment in a regular day.
+>
+> What does one specific moment look like? Be concrete — where are you, what are you doing, what do you see, hear, feel?
+
+**Wait for response.**
+</step>
+
+<step name="capture_scenes">
+After the first scene:
+
+> Good. That's Scene 1.
+>
+> Give me another moment. Different context — maybe a different time of day, different setting, different people. Still concrete, still specific.
+
+**Wait for response.**
+
+Continue capturing until operator has 2-5 scenes. After each:
+
+> **[1] Add another scene** (max 5)
+> **[2] That's enough — move on**
+
+**Wait for response.**
+</step>
+
+<step name="synthesize">
+Read back all scenes, then:
+
+> Your scenes:
+> 1. {scene 1}
+> 2. {scene 2}
+> 3. {scene 3}
+> ...
+>
+> What's the thread? If you had to capture the essence of these moments in one sentence — what's the surface vision?
+
+**Wait for response.**
+
+If the summary is too abstract, push: "Make it more concrete. What would a camera capture?"
+</step>
+
+<step name="confirm_and_lock">
+> ## Your Surface Vision
+>
+> **Scenes:**
+> 1. {scene 1}
+> 2. {scene 2}
+> 3. {scene 3}
+>
+> **Summary:** *"{summary}"*
+>
+> **[1] Lock it in**
+> **[2] Add or replace a scene**
+> **[3] Reword the summary**
+
+**Wait for response.**
+</step>
+
+<step name="lock">
+Surface Vision is locked.
+
+Return to parent workflow with:
+- `scenes`: array of scene strings
+- `summary`: one-sentence synthesis
+- `completed_at`: current ISO date
+
+This phase is complete. Parent workflow resumes.
+</step>
+
+</steps>
+
+<output>
+Surface Vision data: 2-5 scenes + summary sentence, ready for operator.json.
+</output>
+
+<acceptance-criteria>
+- [ ] At least 2 scenes captured (max 5)
+- [ ] Each scene is concrete and sensory, not abstract
+- [ ] Summary captures the thread across scenes
+- [ ] Operator approved the final vision
+</acceptance-criteria>

package/src/commands/orientation/tasks/task-seeding.md

@@ -0,0 +1,93 @@
+<purpose>
+Seed initial tasks under projects after initiatives and project mapping are complete. Tasks are the operator's personal accountability items — concrete must-dos regardless of who or how.
+</purpose>
+
+<user-story>
+As an operator with aligned initiatives and projects, I want to capture the immediate must-do items under each project, so that I have a clear picture of what needs to happen next.
+</user-story>
+
+<when-to-use>
+- Phase 8 of new orientation (after Project Mapping)
+- Operator wants to refresh their task list
+- Composed by new-orientation.md or reorientation.md
+</when-to-use>
+
+<steps>
+
+<step name="frame_and_filter" priority="first">
+> Tasks are YOUR accountability items — things that must get done. Not Claude Code todos. Not aspirational ideas. Concrete next actions.
+>
+> We'll go initiative by initiative, project by project. For each project, I'll show you the current status and ask: "What must get done next?"
+>
+> You can skip any project that doesn't need tasks right now.
+>
+> **[1] Let's go — start with the highest priority initiative**
+> **[2] Skip task seeding for now**
+
+If [2]: Exit gracefully. Tasks can be added anytime via Apex MCP.
+
+**Wait for response.**
+</step>
+
+<step name="iterate_by_initiative">
+For each initiative (highest priority first):
+
+> ## {INI-ID}: {initiative title}
+
+For each project under the initiative:
+
+> **{PRJ-ID}: {project title}** ({status})
+> Next: {current next action from project data}
+> {Blocked: {blocker} if applicable}
+>
+> Any must-do tasks to log under this project?
+> Type them out, or say "skip" to move on.
+
+**Wait for response.**
+
+For each task the operator names:
+- Create via base_add_project(type="task", parent_id="{PRJ-ID}", title="{task}")
+- Confirm: "Logged: {task} under {project}"
+
+Move to next project after each response.
+</step>
+
+<step name="summary">
+After iterating all initiatives and projects:
+
+> ## Tasks Seeded
+>
+> {For each initiative → project → tasks created}
+>
+> **Total:** {N} tasks across {N} projects
+>
+> **[1] Done — lock it in**
+> **[2] Add more to a specific project**
+
+**Wait for response.**
+</step>
+
+<step name="lock">
+Task seeding is locked.
+
+Return to parent workflow with:
+- `tasks_created`: total count
+- `projects_with_tasks`: count of projects that received tasks
+- `completed_at`: current ISO date
+
+This phase is complete. Parent workflow resumes.
+</step>
+
+</steps>
+
+<output>
+Tasks created in Apex via MCP under their parent projects. Operator's immediate accountability items are captured.
+</output>
+
+<acceptance-criteria>
+- [ ] Each initiative's projects presented for task seeding
+- [ ] Tasks created via base_add_project(type="task") with correct parent_id
+- [ ] Operator could skip projects freely
+- [ ] Summary displayed with total counts
+- [ ] NEVER treated tasks as Claude Code internal todos
+</acceptance-criteria>

package/src/commands/orientation/templates/operator-json.md

@@ -0,0 +1,88 @@
+# Operator Profile Template
+
+Output file: `.base/operator.json`
+
+```template
+{
+  "version": 1,
+  "last_updated": "{iso-date}",
+  "hook_active": true,
+  "operator": {
+    "entity_id": "{apex-entity-id}",
+    "name": "{operator-name}"
+  },
+  "deep_why": {
+    "layers": [
+      { "level": 1, "question": "Why do you do what you do?", "answer": "[Layer 1 answer]" },
+      { "level": 2, "question": "But why does that matter?", "answer": "[Layer 2 answer]" },
+      { "level": 3, "question": "But why?", "answer": "[Layer 3 answer]" },
+      { "level": 4, "question": "But why?", "answer": "[Layer 4 answer]" },
+      { "level": 5, "question": "But why?", "answer": "[Layer 5 answer — the root]" }
+    ],
+    "statement": "[Synthesized deep why — one sentence distilled from the 5 layers]",
+    "completed_at": "{iso-date}"
+  },
+  "north_star": {
+    "metric": "[The key metric or outcome everything aligns toward]",
+    "timeframe": "[Target timeframe for this north star]",
+    "rationale": "[Why this metric above all others]",
+    "completed_at": "{iso-date}"
+  },
+  "key_values": {
+    "values": [
+      { "rank": 1, "value": "[Value name]", "meaning": "[What this means to the operator in practice]" },
+      { "rank": 2, "value": "[Value name]", "meaning": "[What this means to the operator in practice]" },
+      { "rank": 3, "value": "[Value name]", "meaning": "[What this means to the operator in practice]" },
+      { "rank": 4, "value": "[Value name]", "meaning": "[What this means to the operator in practice]" },
+      { "rank": 5, "value": "[Value name]", "meaning": "[What this means to the operator in practice]" }
+    ],
+    "completed_at": "{iso-date}"
+  },
+  "elevator_pitch": {
+    "pitch": "[4-floor elevator pitch — who you are, what you do, why it matters, what's next]",
+    "floors": {
+      "floor_1": "[Who you are]",
+      "floor_2": "[What you do]",
+      "floor_3": "[Why it matters]",
+      "floor_4": "[What's next / the ask / the vision]"
+    },
+    "completed_at": "{iso-date}"
+  },
+  "surface_vision": {
+    "scenes": [
+      "[Concrete future moment — specific, sensory, tangible]",
+      "[Another concrete future moment]",
+      "[Another concrete future moment]"
+    ],
+    "summary": "[One sentence that captures the overall surface vision]",
+    "completed_at": "{iso-date}"
+  },
+  "extensions": {}
+}
+```
+
+## Field Documentation
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `version` | integer | Schema version for future migrations |
+| `last_updated` | ISO date | When any section was last modified |
+| `hook_active` | boolean | Controls whether operator hook injects context per prompt |
+| `operator.entity_id` | string | Links to Apex entity (e.g., ENT-001) |
+| `deep_why.layers` | array | The 5-layer "but why?" excavation |
+| `deep_why.statement` | string | Final synthesized deep why |
+| `north_star.metric` | string | The one metric/outcome that matters most |
+| `north_star.timeframe` | string | When this should be achieved |
+| `key_values.values` | array | Ranked top 5, each with practical meaning |
+| `elevator_pitch.floors` | object | 4-part structured pitch |
+| `surface_vision.scenes` | array | 2-5 concrete future moments |
+| `extensions` | object | Open field for future operator metadata |
+
+## Section Specifications
+
+- **deep_why**: All 5 layers must be filled. The statement is a synthesis, not a copy of layer 5.
+- **north_star**: Must be measurable or at minimum clearly evaluable. Timeframe is required.
+- **key_values**: Exactly 5, ranked. Meaning field captures how the value shows up in daily decisions.
+- **elevator_pitch**: Each floor is one sentence max. The full pitch should be speakable in 30 seconds.
+- **surface_vision**: Minimum 2 scenes, maximum 5. Must be concrete and sensory, not abstract aspirations.
+- **extensions**: Reserved for future operator metadata (e.g., strengths profile, archetype data).

package/src/commands/orientation.md

@@ -0,0 +1,87 @@
+<activation>
+## What
+Guided operator identity workflow that produces or updates `.base/operator.json`. Walks the operator through Deep Why, North Star, 5 Key Values, Elevator Pitch, and Surface Vision to create a deep operator profile that aligns initiatives, projects, and tasks.
+
+## When to Use
+- First time setting up a workspace (no operator.json exists)
+- Operator feels disoriented and needs to realign
+- Periodic review of identity anchors (quarterly recommended)
+- After major life or business shifts
+
+## Not For
+- Project-level planning (use /paul:plan)
+- Task tracking updates (use Apex MCP directly)
+- Workspace health checks (use /base:pulse)
+</activation>
+
+<persona>
+## Role
+Orientation guide — facilitates deep self-inquiry without rushing, fluff, or false depth. Holds space for reflection while keeping momentum.
+
+## Style
+- Direct questions, no leading preamble
+- Waits between phases — never auto-advances
+- Uses [N] option brackets for navigation at every decision point
+- Reflects back what the operator said before synthesizing — no assumptions
+- Challenges surface-level answers with "go deeper" follow-ups when warranted
+
+## Expertise
+- Identity frameworks, values clarification, vision anchoring
+- Composable workflow orchestration (parent/child task flow)
+- Operator profile data modeling
+</persona>
+
+<commands>
+| Command | Description | Routes To |
+|---------|-------------|-----------|
+| `/base:orientation` | Full orientation workflow | (this entry point) |
+</commands>
+
+<routing>
+## Always Load
+Nothing — lightweight until invoked.
+
+## Load on Command
+@orientation/tasks/new-orientation.md (when no operator.json exists)
+@orientation/tasks/reorientation.md (when operator.json exists and operator wants to reset)
+
+## Load on Demand
+@orientation/tasks/deep-why.md (Phase 1 of orientation)
+@orientation/tasks/north-star.md (Phase 2 of orientation)
+@orientation/tasks/key-values.md (Phase 3 of orientation)
+@orientation/tasks/elevator-pitch.md (Phase 4 of orientation)
+@orientation/tasks/surface-vision.md (Phase 5 of orientation)
+@orientation/tasks/initiatives.md (Phase 6 of orientation)
+@orientation/tasks/project-mapping.md (Phase 7 of orientation)
+@orientation/tasks/task-seeding.md (Phase 8 of orientation)
+@orientation/templates/operator-json.md (schema reference for operator.json)
+</routing>
+
+<greeting>
+## Orientation Check
+
+Read `.base/operator.json` to determine current state.
+
+**If operator.json does NOT exist:**
+> No operator profile found. This is your first orientation.
+>
+> This workflow will walk you through 8 phases — 5 identity exercises then 3 workspace alignment steps. Defines who you are, where you're headed, and organizes your work to match. Takes 30-60 minutes depending on how deep you go.
+>
+> **[1] Begin orientation**
+> **[2] Not now — exit**
+
+If [1]: Load and execute @orientation/tasks/new-orientation.md
+
+**If operator.json EXISTS:**
+Load and display current profile summary (North Star, Deep Why, Values, Pitch, Vision — one line each).
+
+> Your last orientation was on {last_updated date}.
+>
+> **[1] Full reorientation** — reset everything from scratch
+> **[2] Update a specific section** — keep the rest
+> **[3] Review only** — just look, don't change anything
+
+If [1]: Load and execute @orientation/tasks/reorientation.md
+If [2]: Ask which section, then load that specific task
+If [3]: Display full profile and exit
+</greeting>