The sprint template

The blank impact-sprint template, rendered as the room shows a real sprint. Every dashed box is a gap a holder fills. The canonical copy lives in the LOFL vault at 50-templates/impact-sprint/, v0.2.

← The Sprint Room · Start a sprint · How to use it (README.md)

Be someone

Who holds this sprint, who decides at Close, who witnesses. The room shows roles; a name only when the holder chose it.

From the front matter of _index.md.

Holder
the holder's role, e.g. head of programmes at a cooperative (role — the holder is named only if they choose)
Witness
one outside witness — issues the L1 assessment-promise at Close; a refusal holder too
Scale
internal | client
Window
YYYY-MM-DD → YYYY-MM-DD · buffer to YYYY-MM-DD
Cadence
weekly, <day> — the Spine beat
Lens scope
2–3 lenses watched, + 1 guardrail lens
Where it is
Week 0 · entry gate
Pack
domain pack — csr | ai-governance | … | none
IU — forge · claim · verify
forge: the IU this sprint makes — one promise + its evidence + its deliberation · claim: who claims it, about their own behaviour · verify: who checks it, at what level
Promises kept
none named yet
Partial
none named yet
Released
none named yet
Held dissents
the table is blank — see step 2

Arrive

The felt problem in the holder’s words, the entry gate, and Week 0: intake, red-flag scan, fit memo. The fit memo is the one verdict LOFL issues — about its own participation.

_index.md seed

Impact Sprint NN — system · scale · weeks weeks

Two sentences in the holder's words: the problem as it is felt, by whom, where, how often. Not the solution. Not our words.

The entry gate (answered before the folder exists)

  • Is this The One Thing? — struck 2026-11-08 (correction, template v0.2): dropped as an entry question. Kept here, struck, so the change stays visible.
  • Another sprint running? none | Sprint __ closes on __
  • Who outside my head holds the decision, and when did they say yes? name · date · where (message / call / memo)

The room

Named humans only — team members, decision-owners, witnesses. Beneficiaries are never named here or anywhere in this folder.

RoleWhoIn the room at
System-holdernameevery week
Decision owner (signs at Close)nameW0 · W4 · Close
Runs the weekly turn after LOFL leavesnames, not rolesW1 →
Affected community — at least twotwo named humans, with their consentW1 · W4
Witness / refusal holdername or —Spine beats · Close
ConductorMall

The weeks — conduct, output, gate

WeekDatesConduct (grammar)OutputGate to the next week
0 — Entry gatedatesintake → red-flag scan → fit memo (lofl-impact-sprint instruments)fit memo, or a clean declinemutual go on fit — the one verdict LOFL issues, about its own participation
1 — System framingdatescanvas forward with the two named humans in the room (lofl-os-plan → lofl-7lens-canvas)00-plan.md — Problems→Outcomes Map v0 + scope + stubsplan deliberated; approved by the holder
2 — Theory of systemsdatesdeepen the canvas; first lofl-deliberation beat — the holder's Position, a steelmanned Counter inside the documentsystems map + logic model, Counter includedCounter is strong enough that Dissent is non-empty, or we say why not
3 — Ethics & architecturedatesDPDP stack + NO-PII gate as instruments; DPI rails where real, refused where cargo-cultpilot-ready architecture + compliance checklistno identifiable data is load-bearing anywhere
4 — Pilot design (anti-PoC)datesthe smallest pilot that produces evidence; the holder designs their own Spine (cadence · lens-scope · five fields)pilot plan + holder's Spine v0the holder's team has run ≥ n turns without M
5 — Scale & governance (optional)datescanvas backward; policy / platform / federation pathways; charterscale pathway + charter—
Closedatesurface the five fields → hand the go/no-go back; LOFL signs its own delivery promise04-close-handback.md · 01-promise-charter.md (LOFL's Core)the decision record carries a human's mark, not ours

The weekly unit is one lofl-microskill-loop turn — Align → Plan → Act → Verify → Report at week scale — recorded in 02-week-N-*.md. By Week 4 the holder's team runs the turn without M. That transfer is the product; the documents are its trace.

Stop-condition (written before Week 1)

"We stop this sprint if …" — the holder's sentence. What evidence, what event, what date. A sprint without a stop-condition is a PoC with better vocabulary.

Held dissents (carried beat to beat — see spine/)

DissentRaisedFalsification conditionStatus
…beat date"if X happens by Y, the counter becomes the position"open

Files in this folder

00-plan.md (P1) · 01-promise-charter.md (P2) · 02-week-0-entry-gate.md · 02-week-N-*.md (turns) · spine/03-beat-*.md (P3) · 04-close-handback.md · 05-reporting-pack.md (P4) · _register-pointer.md · optional: registers/claim-register.md · registers/evidence-register.md · registers/decision-register.md

Register stub (for /lofl-doc-flow)

Seed · date:YYYY-MM-DD · impact-sprint-NN · kind: sprint · facing: studio | forge · Stage: Week 0 · Status: 🟡 one line · Next: one line

Related

lofl-impact-sprint · impact-sprint-02 · 00-plan · 01-promise-charter · 04-close-handback · 05-reporting-pack

The file as written (Markdown) →

02-week-0-entry-gate.md seed

Week 0 — Entry gate · Sprint NN · dates

The one verdict LOFL issues in the whole engagement: whether to take the work. Mutual — the holder is deciding too. The three instruments live in the skill (lofl-impact-sprint/instruments/); this file holds their outputs and the decision. Nothing is agreed, priced, or scheduled before this page is complete. At internal scale (M is the holder): run all three on yourself — the red-flag scan is where the self-deception shows; strike the fee line.

1 · Intake (week0-intake-questionnaire.md, sent date, answered date)

Paste the answers whole, in the holder's words. NO-PII: if an answer needed beneficiary-identifiable data to be given, that is itself a finding — log it under flag 4.

A. system and holder · B. history · C. data reality · D. incentives and power · E. decision and capacity · F. expectations — Q1–Q15

2 · Alignment call (date · who was on it)

what was said that the questionnaire didn't carry — in their words

3 · Red-flag scan (week0-red-flag-scan.md) — output block, pasted whole

RED-FLAG SCAN — holder / system — date
Flags raised: #s        Flags cleared on probe: #s
Conditions set: list    Flag-8 logged?: yes/no → running count: n
Disposition set: each raised flag + its disposition, in full — no summary scalar

Flag 8 (verdict expectation) is the one with a memory: two consecutive Week-0 deaths on it force a re-deliberation of the spec's Consensus — recorded in the register, not quietly caved.

4 · Fit memo (week0-fit-memo.md) — variant A proceed | B decline, sent date

paste the memo as sent — it becomes Annex A of any SOW

Conditions of engagement carried into Week 1: plain commitments — "two named community members in the room by Week 1", "one human named to sign at Close"

5 · The strangeness, disclosed (tick only what was said aloud, to the holder, before any fee)

  • No verdicts on your impact — the go/no-go at Close is yours.
  • "Don't build" is a full-fee deliverable.
  • NO-PII — de-identified or synthetic data only.
  • Dissent ships in the documents.
  • Everything versioned, nothing erased.
  • LOFL promises its own delivery only.
  • One sprint at a time — yours is the only one in this window.

6 · Decision

LOFL's verdict on fitin / out — one line
Holder's decisionin / out / later — name · date · where
Fee (client scale)₹XL fixed, set after this memo · exclusive of GST · prices the labour, never the impact
Windowstart → end · buffer to date · weekly session day/time

If out: door state open on condition X / open next cycle / closed for this system. Log flags to the register; increment the flag-8 count if that was the reason. This folder stays — a clean decline is a record, not a deletion.

Register stub (for /lofl-doc-flow)

Tend · date:YYYY-MM-DD · impact-sprint-NN week-0 · fit: in/out · flags: set · flag-8 count: n · next: Week 1 date | door state

Related

_index · 00-plan · lofl-impact-sprint

The file as written (Markdown) →

Plan, then stop at the gate

The Problems→Outcomes Map through the seven lenses, with its own five-part reasons. Nothing is acted on until the holder approves it.

00-plan.md seed

Impact Sprint NN — Plan · phase: Plan · cadence: weekly, <day>

A plan is a Position, not a mandate. It is authored with the holder, argued honestly below, and consented to at the gate. Nothing is Acted or signed until the box is checked. Format is lofl-os-plan's, verbatim; the sprint adds only the prompts in italics.

Pillar 1 — Problems → Outcomes Map (canvas, forward)

Each lens at two scales: the holder's problem now → the outcome sought for the commons. Prose, no scores. Two lenses carry their values in the wording — keep them.

LensProblem (holder scale)Outcome sought (commons scale)
Finance (minimal-sufficient)the least it takes to do this well, and where it comes from
Human (ethic of care)who is cared for; what care looks like for them — in the words of the two humans in the room
Knowledgewhat this gives back — what becomes shareable, CC-BY-SA
Trustwho must trust whom; how it is earned and verifiable; where a witness stands
Impact (IRIS+ noun · SDG)the change claimed as an IRIS+ metric-noun · SDG — look the ID up in the catalogue, don't guess; a noun in the warrant, never a sort key
Systemswhat system this is an instance of — loops, missing voices, power flows, downstream; who loses if it works
Evolutionhow it grows and how we'll know — the longitudinal axis the Spine watches

Sprint Scope

  • Cadence (how often the Spine deliberates): …
  • Lens-scope (which lenses this sprint watches; one guardrail lens): …
  • Minimal-sufficient resource: people · hours · tools · data (de-identified or synthetic only) · money — the least that works
  • Promises I intend to make (named now, signed at Act in 01-promise-charter.md):
  • LOFL, about its own delivery: artifact · date · gate
  • holder, about their own behaviour — shape only, their words at Act: …
  • Missing voice, on purpose: who is not in the room and why — e.g. beneficiaries (NO-PII); name the downstream voice

Pillar 2 — Promise Charter (STUB — filled at Act by lofl-promise-ledger)

  1. Issuer identity: · 2. Claim: · 3. Evidence pointer (IRIS+ noun · SDG): · 4. Self-deliberation: · 5. Timestamp: · 6. Self-signature: · 7. Supersession path:

Pillar 3 — M&E Spine (STUB — run at Verify by lofl-deliberation, one beat per cadence tick in spine/)

  • Cadence: … · Lens-scope: …
  • Fields per beat: Position · Evidence · Counter-Argument · Consensus · Dissent

Plan deliberation (run before approval)

  • Position. the plan as a defended choice — scope, weeks, lenses, resource
  • Evidence. why this scope — intake answers, the felt problem, what dead pilots taught
  • Counter-Argument (steelmanned). the strongest honest case against running this sprint at all, or in this shape
  • Consensus. what holds after the argument — real agreement only
  • Dissent (surfaced, not averaged). what stays unresolved — carried into _index.md → Held dissents, with a falsification condition

Approval

  • Approved by holder on ____ → hand off to Act (01-promise-charter.md) and Verify (spine/).
  • The two named humans from the affected community have read the Human lens row and corrected it.

Until both are checked: plan only. Nothing signed.

Register stub (for /lofl-doc-flow)

Tend · date:YYYY-MM-DD · impact-sprint-NN 00-plan v0 · status: seed · supersedes: none · open: (a) holder approval; (b) Human-lens read by the two named humans; (c) IRIS+ ID looked up.

Related

_index · 01-promise-charter · lofl-os-plan · lofl-7lens-canvas · lofl-deliberation

The file as written (Markdown) →

Promise

Each promise is about the promiser’s own behaviour: LOFL about its delivery, the holder — if they choose — about theirs. Nobody co-signs anybody.

01-promise-charter.md seed

Impact Sprint NN — Promise Charter · Pillar 2

Promise Theory governs the whole sprint: an agent promises only about its own behaviour, and no obligation is imposed from outside. LOFL promises its delivery — dates, artifacts, gates. The holder promises, if at all, about their own behaviour, in their own words, self-signed. Nobody co-signs anybody. A promise is never deleted; it is superseded.

The Core — seven fields, all required, completable by one person alone. The Envelope (a witness's five fields about observing the promise) is optional and never required. Core without Envelope, never the reverse.


Promise P1 — LOFL, about its own delivery

Field
1. Issuer identityLeap of Faith Labs (OPC) Pvt Ltd · M · did:… or equivalent
2. ClaimI will deliver artifact by date, gated on gate. — one clear statement about our behaviour, never the holder's outcome
3. Evidence pointerpath or hash of the artifact · IRIS+ noun: … · SDG: … — a noun in the warrant, never a sort key
4. Self-deliberation recordPosition: … · Evidence: … · Counter: … · Consensus: … · Dissent: …
5. TimestampYYYY-MM-DD HH:MM IST · cycle: Sprint NN, Week n
6. Self-signaturesignature over fields 1–5 — the human presses the mark
7. Supersession path→ empty until a later promise supersedes this one; never deleted

Class: Core only | Core + Witnessed · Witness (if any): name — their five fields live in spine/ as an inter-personal beat, never here.


Promise P2 — LOFL, about its own delivery

(copy the block above; one Core per promise — the Sunday-Spine-style "the weekly beat itself" is a legitimate promise)


The holder's promise (at Close, optional, theirs)

Shape only — not written by us. If holder chooses to promise, it is about their own behaviour after the sprint (e.g. running the weekly turn for ninety days), in their words, signed by them, with the same seven fields. LOFL never drafts the Claim. LOFL never co-signs. It lands here only because they put it here.

Field
1. Issuer identityholder
2. Claimtheirs
3. Evidence pointertheirs
4. Self-deliberation recordtheirs — five fields
5. Timestamp
6. Self-signature
7. Supersession path

Rules that hold on this page

  • No scalar anywhere: no score on a promise, no ranking of promises, no leaderboard. Aggregation, if any, presents a set.
  • A promise about someone else's outcome is not a promise; it is a target. Strike it.
  • Every promise carries its own five-field deliberation before it is signed (field 4) — a promise without a Counter is bare testimony.
  • Supersession only: a promise that no longer holds is superseded by a new one with a pointer back. Field 7 is the sprint's Evolution lens made concrete.

Register stub (for /lofl-doc-flow)

Tend · date:YYYY-MM-DD · impact-sprint-NN 01-promise-charter · promises signed: set — list them, no count-as-score · superseded: … · open: …

Related

_index · 00-plan · 04-close-handback · lofl-promise-ledger · lofl-deliberation

The file as written (Markdown) →

Do the work, keep the trace

One practice turn a week. By Week 4 the holder’s team runs it without LOFL — that transfer is the product. Evidence is a pointer, never raw data about people served.

02-week-turn.md seed

Week n — conduct · Sprint NN · dates

Copy this file once per week (1–5). The week's conduct comes from the table in _index.md; the shape of the week is always one microskill-loop turn. The point of the turn is not the document — it is that by Week 4 the holder's team runs it without M. Record who ran what.

This week's conduct (from _index.md): 1 System framing — canvas forward · 2 Theory of systems — first deliberation beat, Counter inside · 3 Ethics & architecture — DPDP + NO-PII gate, DPI rails where real · 4 Pilot design — anti-PoC, holder designs own Spine · 5 Scale & governance — canvas backward Output due: from the table · Gate to next week: from the table

In the room

WhoRolePresent
holdersystem-holdery/n
namesrun the turn after LOFLy/n
two named humansaffected communityy/n — required in Weeks 1 and 4
Mconductor

The turn

Align — the one falsifiable outcome-noun this week serves:

e.g. "a Problems→Outcomes Map the two named humans have corrected" — a noun, not a feeling

Plan — the smallest rep at minimal-sufficient resource:

what gets done in the session, what async, by whom; what is not done this week

Act — what was actually done (date · hours):

the work, plainly. Who held the pen. Where M stepped back on purpose.

Verify — the evidence, as a UIX set (never a verdict):

Element (the practice / artifact)WITNESSED_BYDISSENTS_FROMSUPERSEDES
…who/what checked itwhat failed or disagreed — at equal weightwhat this replaces

Report — the set, read aloud to the holder at the end of the session:

what the rep showed · what witnessed it · what it leaves open

Capacity transfer (the actual product)

  • Turns run by the holder's team without M so far: list by date — a set, not a count-as-score
  • What they could not yet do alone: …
  • What M will not do next week so that they do: …

Week-specific instruments

  • Week 2: the first Spine beat — file it in spine/03-beat-date.md; the steelmanned Counter goes into the systems document, not a footnote.
  • Week 3: DPDP stack checklist attached: link · NO-PII gate result: no identifiable data is load-bearing / it is — name where, and what changes · Rails: APAAR / ONEST / Beckn / DIKSHA — used where real, refused where cargo-cult, one line each
  • Week 4: the holder's own Spine v0 — cadence … · lens-scope … · five fields · who runs the beat: name. The pilot's stop-condition, verbatim: "…".

Gate

  • Output due this week exists, versioned: path
  • Gate condition met: from the table — or, honestly: not met → next week is a redo, not a stack.

Register stub (for /lofl-doc-flow)

Tend · date:YYYY-MM-DD · impact-sprint-NN week-n · output: path · gate: met / not met — why · turns without M: set

Related

_index · 00-plan · spine/_spine · lofl-microskill-loop

The file as written (Markdown) →

registers/evidence-register.md seed optional

Evidence register · Sprint NN

Optional. Pointers to records and artifacts — never the raw data. NO-PII: nothing about the people the holder serves goes here; a pointer to a de-identified file, or its sha256, is enough. In the Sprint Room it sits under step 5, Do the work, keep the trace.

EvidenceKindSupportsRestrictionsState
file or path · sha256thinking · trace · artifact · witnesswhich claim or promisenone known · confidential · de-identifiedavailable · pending · withdrawn

Missing evidence worth noticing

  • what would move a claim from bounded-testimony to evidence-bound, and who would have to produce it

Related

../_index · claim-register · ../01-promise-charter · ../spine/_spine

The file as written (Markdown) →

Check, never score

The Spine: a five-field deliberation at the sprint’s cadence. Position, Evidence, Counter, Consensus, Dissent. Dissent is carried, never averaged.

spine/_spine.md seed

The Spine · Sprint NN

Cadence: weekly, <day> · Lens-scope: lenses watched + guardrail lens · Beats in window: K · Series stops: date — the sprint window closed; the holder's own Spine continues if they built one in Week 4

A sequence of five-field records at the chosen cadence IS the M&E artefact. There is no dashboard. If a beat is run unattended or the vault is unreachable, the beat is still written and filed later — the rhythm is the point, not the tooling.

Beat index

#DateLensesPosition (short)Dissent surfacedFile
1date……yes — what / none, Counter judged strong enough03-beat-date
2

Held-dissent ledger (the sprint's memory)

DissentRaisedFalsification conditionBeats carriedStatus
…beat k…k, k+1 …open / tested / closed

Witness beats (inter-personal)

WitnessPromise observedFile
namePn03-beat-date-witness-name

Related

../_index · ../00-plan · ../01-promise-charter · 03-spine-beat (the blank)

The file as written (Markdown) →

spine/03-spine-beat.md seed

Deliberation: claim in a few words

Copy this file once per cadence tick into spine/ as 03-beat-date.md. The Spine is a rhythm, not a dashboard — cadence you chose, over the lenses you chose, five fields every time, Dissent surfaced and never averaged. The format is lofl-deliberation's, verbatim; the sprint adds the promise check and the carried-dissent ledger beneath it.

Scale: Intra-personal (self) / Inter-personal (witness of: <promise id>) Cycle / Date: Sprint NN · beat k of K · date Lens-scope: the lenses this beat covers — from _index.md; name the guardrail lens

Position

the claim — one thing that could be wrong; if this is a selection of metric/lenses, state it as a choice being defended

Evidence

  • grounds: trace / observation / artefact — paths, not adjectives
  • IRIS+ metric (noun): standard metric · SDG(s): aligned goals ← noun, not a score

Counter-Argument (steelmanned)

the strongest case against the Position — made in good faith. If you cannot write one, the Position is not yet a claim.

Consensus

what holds after the argument — real agreement only

Dissent

what did NOT resolve — surfaced and kept. Do not average it away. If none, say so and ask whether the Counter was strong enough.


Promises checked this beat (a set — never a percentage)

PromiseClaim (short)DueThis beat: artifact present / absent / supersededPointer
P1…datepresent — path / absent — since when / superseded → Pn…
P2

An absent artifact is written as absent with the date it became overdue. It is not a red number; it is a sentence. "No recorded completion status" is a legitimate entry and a signal.

Held dissents (carried forward from earlier beats)

DissentRaisedFalsification conditionThis beat
…beat date"if X by Y, the counter becomes the position"untested — why / tested — what happened / closed — by what evidence

A dissent carried twice untested is itself a finding: name what would have tested it and who did not do it.

Witness (Envelope — optional, only if a witness observed this cycle)

Witness: name · their five fields about their observation of the promise live in a separate inter-personal beat: 03-beat-date-witness-name.md. Same grammar, other scale. Never merged into this one.

Register stub (for /lofl-doc-flow)

Tend · date:YYYY-MM-DD · impact-sprint-NN beat k · lenses: … · promises: set · dissent carried: n named · next beat: date

Related

../_index · ../01-promise-charter · lofl-deliberation · lofl-promise-ledger

The file as written (Markdown) →

Record, never rewrite

The dated record, only ever added to. Claims and decisions change state only when the record underneath them changes; anything corrected is superseded.

_register-pointer.md evergreen

Register pointer — impact-sprint-NN

One source of truth: LOFL Cards/lofl-deliverables.md in the vault. This folder keeps the sprint's own files; it never keeps its own register.

Proposed row (seed at Week 0): kind: sprint · facing: studio | forge · Stage: Week 0 · Status: 🟡 one line · Next: one line · Folder: 10-projects/impact-sprint-NN-slug/

Dated notes (append, never erase)

date:YYYY-MM-DD — Week 0 opened. holder · system in one line · scale · window. Instruments run: intake date, call date, scan flags raised / cleared, fit memo variant A/B sent date. Decision: in/out. Flag-8 count: n.

date — Week 1. …

date — Close. Decision holder's word, signed by name. LOFL promise Pn self-signed. Dissent shipped: named. Door: state.

The file as written (Markdown) →

registers/claim-register.md seed optional

Claim register · Sprint NN

Optional. Use it when the sprint will make public claims — about a capability, a practice, a result. It is not a scorecard: it records the state each claim is in, and the record behind that state. In the Sprint Room it sits under step 7, Record.

Claim states

  • evidence-bound — an inspectable evidence path exists (a pointer in evidence-register.md)
  • bounded-testimony — a real claim, but public checking is limited by confidentiality, a missing public artifact, or another stated boundary
  • practice — being learned or practised; not shown as a capability yet
  • aspiration — a direction wanted; not a capability claim
  • superseded — replaced by a later claim, kept in the record

Register

Claim / domainStateEvidence pointerLimitation / dissentSupersession
…stateevidence row or pathwhat this claim must not be read as—

Rule

A sentence does not move state because it sounds convincing. State changes only when the record underneath it changes — and then the old row is superseded, not edited.

Related

../_index · evidence-register · decision-register · ../01-promise-charter

The file as written (Markdown) →

registers/decision-register.md seed optional

Decision register · Sprint NN

Optional. Only decisions that were actually made. Questions and options belong in a Spine beat until a decision exists. The Close decision itself lives in 04-close-handback.md — this register holds the smaller ones on the way. In the Sprint Room it sits under step 7, Record.

DecisionDateMade byEvidence / deliberationRevisit conditionSuperseded by
…YYYY-MM-DDholder role or namespine/03-beat-…"revisit if …"

Open decisions

  • what is still open, and which beat holds the deliberation — dissent kept, not averaged

Related

../_index · claim-register · evidence-register · ../04-close-handback

The file as written (Markdown) →

Report, release, begin again

The decision is handed back; a human presses the mark. LOFL signs a promise about its own delivery only. Each promise is named kept, partial or released.

04-close-handback.md seed

Close — the handback · Sprint NN · date

The sprint ends by handing the decision back. LOFL surfaces Position · Evidence · Counter · Consensus · Dissent on the pilot question, then steps aside. The holder decides — go, no-go, or don't build — and a human presses that mark. LOFL signs a promise about its own delivery, and nothing else. If the honest answer is "don't build," this page is the deliverable, at full fee, and it is written with the same care as a go.

1 · The pilot question, surfaced (five fields — lofl-deliberation)

Position. the pilot as designed in Week 4, as a defended choice — or "don't build", as a defended choice Evidence. the set — the Map, the systems model with its Counter, the Week-3 checklist, the pilot plan, the beats; IRIS+ noun · SDG Counter-Argument (steelmanned). the strongest case against the Position — inside this document, at full strength Consensus. what the room actually agreed — the holder's team, the two named humans, M Dissent. what did not resolve, by name, with who holds it — it ships

2 · The decision record — the holder's, not ours

Decisiongo / no-go / don't build / go with conditions
In the holder's words"…"
Conditions the holder set on themselves…
Stop-condition carried into the pilot (verbatim from _index.md)"…"
Signed bydecision owner — name · date · the mark — a signature, a sent message, a minute; never a machine
Dissent acknowledged as shippingdecision owner initials

LOFL does not sign this table. If the holder asks LOFL to "recommend", the answer is the five fields above, read aloud again.

3 · LOFL's promise — about its own delivery only (lofl-promise-ledger, Core)

Filed in 01-promise-charter.md as Promise Pn; summarised here:

I delivered artifacts — the set by dates, through gates …. Where I did not: what, and the supersession pointer. Self-signed date. No co-signature. Outcomes are the holder's to promise.

4 · What leaves with the holder (all client-owned; LOFL keeps only the negotiated right to publish de-identified patterns, CC-BY-SA)

  • 00-plan.md — Problems→Outcomes Map, deliberated and approved
  • the systems map + logic model, with the Counter inside
  • the Week-3 architecture + DPDP/NO-PII checklist
  • the pilot plan, with its stop-condition, and the holder's own Spine v0 (cadence · lens-scope · five fields · who runs it)
  • this decision record
  • if Week 5 ran: the scale pathway + governance charter

5 · The ninety days after

Who runs the weekly turn without LOFLnames
First beat of the holder's own Spinedate
What LOFL will not do (so that they do)…
Door state for a further engagementopen on condition X / next cycle / closed — this system is theirs now
De-identified pattern LOFL may publish (agreed)one line, or "none"

6 · Supersession

This record supersedes: earlier decision drafts, if any. It is superseded by: empty — a later record points back here. Nothing on this page is deleted.

Register stub (for /lofl-doc-flow)

Close · date:YYYY-MM-DD · impact-sprint-NN · decision: holder's, one word · LOFL promise: Pn signed · dissent shipped: n named · next: 05-reporting-pack after the pilot runs; door: state

Related

_index · 01-promise-charter · spine/_spine · 05-reporting-pack · lofl-deliberation · lofl-promise-ledger

The file as written (Markdown) →

05-reporting-pack.md seed

Reporting Pack · Sprint NN · Pillar 4

The same seven lenses that framed the problem in 00-plan.md, read backward to report what evolved: Evolution · Systems · Impact · Trust · Knowledge · Care · Optimal resource. That order is the litany — the report visibly mirrors the framing, so the two are commensurable by construction. Both scales again: the holder, then the commons. Evidence is a set; nothing here is a score. lofl-artefact-flow renders this into the Impact-Study Pack for an assessor only after this page exists.

Phase: Backward — Reporting Pack · Date: date · Reports on: 00-plan.md vn of date · Lenses foregrounded: which were load-bearing, and why, briefly

Evolution

How did it grow, and how do we know — the longitudinal axis, beat by beat. What the Week-1 map said would move; what the beats show moved, held, or reversed. Held dissents: tested or not. — holder scale: … · commons scale: …

Systems

What system this turned out to be an instance of. Loops that closed; the missing voice — was it ever heard; power flows — who lost, and were they in the conversation; downstream effects observed. — holder scale: … · commons scale: …

Impact

The change claimed, as an IRIS+ noun · SDG — the same noun as in the Plan, or the supersession that replaced it and why. Evidence as a set of artifacts and beats, with pointers. No number that reads as a verdict. — IRIS+: noun · ID looked up · SDG: … · evidence set: paths

Trust

Who trusted whom, and how it was verified — promises signed, witnessed beats, what a witness's five fields said that ours did not. Where trust was withheld, and whether that was right. — holder scale: … · commons scale: …

Knowledge

What went back to the commons — the de-identified pattern LOFL may publish (agreed at Close), the artifacts the holder now owns, the cards forged, all CC-BY-SA. What was learned that the next sprint's Week 0 should ask. — holder scale: … · commons scale: …

Care (Human)

Who was cared for, and what care actually looked like — in the words of the two named humans, read back to them. Where the ethic of care cost something (time, scope, a feature refused). What the pilot's stop-condition protected. — holder scale: … · commons scale: …

Optimal resource (Finance)

What it actually took against the minimal-sufficient resource named in the Plan — hours, money, tools, data. Where sufficiency held; where it slipped and why. The fee, as the price of labour, never of impact. — planned: … · actual: …


What this pack may claim, and may not

May: that the sprint ran to its gates; that the holder decided; that the evidence set exists at these pointers; that dissent shipped. May not: any scalar of the holder's impact; any outcome the holder did not themselves promise; any claim without a pointer.

Hand-off → Impact-Study Pack (lofl-artefact-flow)

Gate check: pilot ran y/n · beats exist n · LOFL's VICs self-signed y/n · this backward read complete y/n. All four, or do not render. Audience: SSE / CSR assessor → PDF · partner → live artifact.

Register stub (for /lofl-doc-flow)

Report · date:YYYY-MM-DD · impact-sprint-NN 05-reporting-pack v0 · reports on 00-plan vn · evidence set: paths · study pack: rendered / gated — what's missing

Related

_index · 00-plan · 04-close-handback · spine/_spine · lofl-7lens-canvas · lofl-artefact-flow

The file as written (Markdown) →