Engagement northstar: naming, properties, movement contract

[ojfbot]

Question

What is the engagement's northstar — its slug/name (purpose-named, not client-named? cf. feedback: name-by-purpose), its level (l1), its measurable properties (customer-value-in-their-numbers? dossier genre coverage G1–G6? playbook-shadow fill?), current/target values, and its movement contract — so engagement slices ride roadmap/day-run/odometer machinery?

Type

grilling (HITL, /grill-with-docs)

Context

Map: decisions/wayfinder/texas-rr-engagement.md (#344). Registry: core/decisions/northstar/README.md (19 entries, no engagement northstar). Ruler: decisions/research/2026-08-01-fde-deliverables-audit.md. Vault brief: selfco wiki/synthesis/texas-rr-engagement-brief. Slice sessions never write northstar current: — movement proposals only.

Blocked by

None — on the frontier.

Resolution (filled at close)

—

[ojfbot]

Resolution (2026-08-01, operator-grilled this session; landed in PR #357 / c63de2b)

Slug/name: l1-fieldwork-1 — engagement-scoped, purpose-named (name-by-purpose: "fieldwork" = forward-deployed field engagement), ordinal keeps the client name out. Repo (app) = fieldwork-1, private (#349 is now unblocked and names itself from this ruling). Retires at sustainment/exit; engagement #2 mints l1-fieldwork-2.

Level: L1, ladders_up_to: l2-ojfbot. Registered as the 20th entry in decisions/northstar/README.md (client-anonymous: slug/path/comment only).

Properties (5 — ALL NUMERICS PROPOSED, operator calibrates; capture-agent precedent):

Id	Axis	current	ladders
P1	The full engagement arc is traversed (lead→research→discovery→scoped delivery→sustainment; fed by #350's gates)	15	ns:l2-ojfbot#P1
P2	Value lands in the customer's numbers (their units, customer-accepted deltas — never tokens)	0	ns:l2-ojfbot#P1
P3	The dossier is genre-complete (G1–G6 per the deliverables audit ruler)	0	ns:l2-ojfbot#P1
P4	The playbook shadow fills per completed stage (capture strictly trails evidence)	0	ns:l2-ojfbot#P2
P5	Delivery is mechanized and auditable — recursive SE (operator elevation, this session)	0	ns:l2-ojfbot#P2

P5 provenance: mid-session the operator elevated the NASA SEH process model (system design top-down, product realization bottom-up, technical management cross-cutting) for the self-built components serving the engagement — least manual effort, most mechanical automation / auditability / transparency / accountability / accuracy. This refines — does not reverse — the charting ruling (which ruled out literal ISO-15288 client-facing stage naming). The 17-process mapping detail is widened into #350's scope.

Movement contract: currents are operator-asserted only; slice sessions NEVER write current: — every engagement PR carries Movement proposal: ns:l1-fieldwork-1#Pn N% -> M% — evidence: …; record-movement.mjs appends status.jsonl from merged PRs only; a slice that cannot name its property does not dispatch (work with no metric attached doesn't start). Delivery roadmap is minted at map handoff, not here.

Northstar FILE: lands in the private repo at fieldwork-1/.claude/northstar.md via #349 (client-named baselines go there, never in core). Client-light draft posted on #349. Interim absent-checkout = shadow WARN (verified: northstar-lint --check 0 errors).

Map tending (same PR): gist appended to Decisions so far; two fog items graduated (seh tie-in → P5 + widened #350; re-anchor → ruled YES, executes at #349 when ns:l1-fieldwork-1 resolves); post-#345 frontier recorded; new task ticket #356 (public-map client-intel sanitization) created and wired as a #344 child per the client-data ruling.