Production Measurement: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Created page with "= Production Measurement Curriculum (FBCC Boot Camp) = == Purpose == Production Measurement is a core competency of the Future Builders Boot Camp. Participants learn how to make real work legible, verifiable, and schedulable under production conditions. Production is defined as a **verifiable state change of a defined scope over time**. Effort, intent, and explanation do not count as production unless supported by evidence. This curriculum is not a separate track....")
 
Line 12: Line 12:


== Learning Outcomes ==
== Learning Outcomes ==
By the end of the Boot Camp, each participant can:
By the end of this Boot Camp session, each participant can:
* Define bounded production scopes
* Define bounded production scopes
* Capture timestamped evidence of work
* Capture timestamped evidence of work

Revision as of 07:13, 1 February 2026

Production Measurement Curriculum (FBCC Boot Camp)

Purpose

Production Measurement is a core competency of the Future Builders Boot Camp. Participants learn how to make real work legible, verifiable, and schedulable under production conditions.

Production is defined as a **verifiable state change of a defined scope over time**. Effort, intent, and explanation do not count as production unless supported by evidence.

This curriculum is not a separate track. It is how building is done at Open Source Ecology.

Learning Outcomes

By the end of this Boot Camp session, each participant can:

  • Define bounded production scopes
  • Capture timestamped evidence of work
  • Log independently verifiable Production Data
  • Pass quality gates tied to acceptance criteria
  • Understand burndown as time reduction with practice
  • Produce audit-ready records suitable for production planning

Core Principle

If the system cannot see the work, the system cannot rely on it.

Curriculum Structure

The Production Measurement curriculum is embedded directly into FBCC builds and runs in parallel with physical construction work.

Explicit instruction time is minimal. Application is continuous.

Day 0: Why Production Measurement Exists

  • Production is not activity; it is state change
  • Production requires a start state, an end state, and time
  • Measurement protects builders from ambiguity and favoritism
  • Measurement is not grading, surveillance, or speed obsession

Key sentence: Production is measured by how quickly and reliably defined scopes reach an accepted state.

Day 1: Production Scope Definition

Participants learn how to define a production scope.

A valid scope:

  • Has a clear start state
  • Has a clear end state
  • Has objective acceptance criteria
  • Can be repeated

Examples:

  • Invalid: Worked on framing
  • Valid: Framed WALL-MOD-2x6-8FT-V1 from bare deck to sheathed, square, nailed per spec

Each participant must rewrite at least one real FBCC task as a bounded scope.

Day 2: Time and Evidence Capture

Participants learn how production time is measured.

Rules:

  • Time is captured by system timestamps, not self-report
  • Evidence must show before and after states
  • Scope ID must be visible in evidence
  • Partial completion does not stop the clock

Each participant logs:

  • Scope start
  • Timestamped before-state image
  • Scope completion
  • Timestamped after-state image

Day 3: Quality Gates and Acceptance

Participants learn that production completes only at acceptance.

Rules:

  • QC is objective, not opinion
  • Failed QC extends production time
  • Rework time is counted
  • No acceptance means no completion

Participants experience:

  • Passed scopes
  • Failed scopes
  • Rework and reinspection
  • Time impact of quality errors

Day 4: Burndown and Learning

Participants learn how burndown works.

Burndown is defined as:

  • Cycle-time reduction on identical scopes
  • With unchanged quality requirements
  • Measured using median time over multiple repetitions

Rules:

  • Burndown applies only to identical scope IDs
  • Best-time runs do not count
  • Variance matters more than hero speed

Participants repeat a scope and observe natural time reduction.

Day 5: Production Data Logging

Participants learn that documentation is part of production.

A valid Production Data log includes:

  • Builder identity
  • Scope ID
  • Start and end timestamps
  • QC status
  • Evidence tied to the scope

Logs must be independently auditable by someone not present during the build.

If another builder can audit the record without explanation, it passes.

Evidence and Verification Standard

Production Data is considered verifiable only if:

  • Evidence is timestamped
  • Scope ID is visible
  • State change is observable
  • QC acceptance is recorded
  • Records support burndown accounting

Narratives without evidence do not count.

Relationship to Test-Out and Earning

No participant may test out as a Production Builder unless their work is:

  • Documented transparently
  • Verifiably timestamped
  • Suitable for burndown analysis

Production Measurement is a prerequisite for earning on production scopes.

Cultural Rule

If the bay camera did not see it, the system did not see it.

Outcome

Participants exit FBCC with:

  • Production literacy
  • Accountability clarity
  • Verifiable contribution records
  • A clear path to Production Builder test-out

This curriculum establishes the foundation for reliable production, automated QC, and scalable enterprise formation.