Skip to content
LOCK
Lock Method
Lock reference · Draft
v0.1.0

Discover and Synthesize Process Evidence

Find process knowledge in Lock’s existing Book Profiles, Bicycle Guides, CanonicAI outputs, and Corpus Library without creating a second corpus or mistaking extracted material for a Lock standard.

Adopt · export.mdAdopt · export.jsonDraft reference — not a fitted standard

Profile

Purpose

Create a traceable, rights-aware evidence packet that lets a Lock architect synthesize or revise a connected management process efficiently and honestly.

Intended outcome

A reviewed evidence packet with stable source identities, process candidates, agreements, tensions, applicability limits, provenance, rights constraints, and explicit unanswered questions ready for Lock synthesis.

Accountable
Lock method owner
Operator
Process evidence analyst
Use when
  • — A management process is selected from the process inventory for development.
  • — A reference process needs stronger evidence or a scheduled evidence refresh.
  • — A source, Book Profile, Bicycle Guide, or CanonicAI extraction changes materially.
  • — A client context raises a question not adequately supported by the current evidence packet.

Entry gate

  • A process-inventory ID, research question, intended decision, scope, and accountable owner are recorded.
  • Existing Lock standards and evidence are checked before new retrieval begins.
  • Relevant upstream systems and permitted-use boundaries are known or explicitly unresolved.

Exit gate

  • The evidence packet has stable source IDs, versions or hashes, retrieval dates, rights labels, claim mappings, and review state.
  • Agreements, contradictions, applicability limits, gaps, and Lock judgment are distinguishable.
  • The packet is accepted for synthesis, returned for targeted research, or closed with a documented rationale.

Flow · 6 controlled steps

  1. 01

    Frame the process research question

    Prevent broad literature search from becoming an unbounded collection exercise.

    • — Resolve the management-process inventory ID and neighboring processes.
    • — State the decision the evidence must support.
    • — Define required process elements, contexts, exclusions, consequence level, and stop conditions.
    • — Review the current Lock standard and evidence packet before searching upstream systems.
    Responsible
    Process architect
    Output
    Process Evidence Request
    Decision
    Is new or refreshed evidence necessary to support a defined process decision?
  2. 02

    Inventory existing upstream material

    Reuse canonical extracts and synthesis before returning to original source material.

    • — Query Book Profiles and Bicycle Guides by process purpose, outcomes, decisions, roles, artifacts, failure modes, and adjacent terminology.
    • — Locate CanonicAI canonical candidates and Corpus Library identities.
    • — Record stable IDs, versions, source locations, review states, and rights labels.
    • — Identify missing, stale, inaccessible, disputed, or duplicate records.
    Responsible
    Process evidence analyst
    Output
    Upstream Evidence Inventory
    Decision
    Does the upstream estate provide sufficient canonical material?
  3. 03

    Retrieve and normalize candidate evidence

    Create comparable process candidates while preserving what each source actually says.

    • — Retrieve the minimum relevant structured records and permitted source passages.
    • — Map candidates to purpose, gates, steps, decisions, roles, data, systems, controls, measures, connections, and exceptions.
    • — Retain verbatim excerpts only when necessary and permitted.
    • — Label paraphrase, extraction, synthesis, practitioner judgment, and Lock judgment separately.
    Responsible
    Process evidence analyst
    Output
    Normalized Evidence Candidates
    Decision
    Can each candidate claim be traced and used within its rights boundary?
  4. 04

    Compare evidence and evaluate transfer

    Distinguish recurring principles from context-specific practice and unsupported convention.

    • — Identify agreement, contradiction, missing interfaces, and differences in assumptions.
    • — Evaluate source quality, recency, directness, consequence, and transfer to target company contexts.
    • — Seek disconfirming evidence and common failure modes.
    • — Separate universal mechanism, configurable choice, industry constraint, and unresolved question.
    Responsible
    Lock method owner
    Output
    Evidence Comparison and Gap Record
    Decision
    Is the evidence adequate and transferable enough for Lock synthesis?
  5. 05

    Assemble and review the evidence packet

    Deliver an inspectable input to process synthesis rather than a folder of undifferentiated notes.

    • — Assemble source registry, claim mappings, process candidates, comparison, gaps, rights, and review notes.
    • — Deduplicate by stable source and candidate identity.
    • — Run practitioner, rights, legal, safety, quality, or regulatory review when triggered.
    • — Record acceptance, restrictions, disputes, and expiry or refresh triggers.
    Responsible
    Lock method owner
    Output
    Versioned Process Evidence Packet
    Decision
    May this packet be used to create or revise a Lock draft?
  6. 06

    Transfer to synthesis and improve discovery

    Close the loop between research effort, process quality, and the upstream portfolio systems.

    • — Transfer the packet to the reference-process lifecycle with unresolved questions visible.
    • — Record which searches, terms, systems, and sources were useful or wasteful.
    • — Propose upstream metadata or extraction improvements without changing upstream truth.
    • — Set refresh triggers based on source change, process performance, risk, or scheduled review.
    Responsible
    Process evidence analyst
    Output
    Synthesis Handoff · Discovery Improvement Record
    Decision
    What follow-up does this discovery cycle justify?

Connections

downstream

Redesign Work and Workflow

Transfers the accepted evidence packet, restrictions, gaps, disputes, review state, and refresh triggers for original Lock process design or redesign.

Trigger · The evidence packet is accepted for synthesis.

Carries · Process Evidence Packet · Synthesis Handoff

Seams · 10 hops within 2 steps

Upstream and downstream neighbourhood over public reference processes only. Each hop shows the trigger, carried objects, and what the receiving process loses if the producing step is skipped.

downstream · hop 1

Open process

Architect a People Management System

Trigger · Architecture requires evidence beyond the current approved estate.

Carries · Process Evidence Packet

If the handoff from Discover and Synthesize Process Evidence is skipped, Architect a People Management System loses Process Evidence Packet.

downstream · hop 1

Open process

Design and Govern a People Policy

Trigger · Policy design or review requires evidence beyond authoritative requirements and current operating records.

Carries · Process Evidence Packet

If the handoff from Discover and Synthesize Process Evidence is skipped, Design and Govern a People Policy loses Process Evidence Packet.

downstream · hop 1

Open process

Design and Validate a Recurring Human Practice

Trigger · The practice design requires new or refreshed evidence.

Carries · Process Evidence Packet

If the handoff from Discover and Synthesize Process Evidence is skipped, Design and Validate a Recurring Human Practice loses Process Evidence Packet.

downstream · hop 1

Open process

Redesign Work and Workflow

Trigger · The evidence packet is accepted for synthesis.

Carries · Process Evidence Packet · Synthesis Handoff

If Transfer to synthesis and improve discovery is skipped, Redesign Work and Workflow loses Process Evidence Packet · Synthesis Handoff.

downstream · hop 2

Open process

Approve Workforce Need and Headcount

Trigger · The approved response includes redesigning, reallocating, stopping, or automating work.

Carries · Workforce Decision · Capacity and Capability Assessment

If Assess capacity and capability is skipped, Redesign Work and Workflow loses Workforce Decision · Capacity and Capability Assessment.

downstream · hop 2

Open process

Implement a Business System

Trigger · The approved workflow requires system configuration, integration, or automation.

Carries · Approved Workflow Specification

If Validate and authorize the design is skipped, Implement a Business System loses Approved Workflow Specification.

downstream · hop 2

Open process

Manage Team Capacity and Priorities

Trigger · Capacity review identifies work or process design as a material cause.

Carries · Capacity and Priority Review · Improvement Handoff

If Review outcomes and improve capacity design is skipped, Redesign Work and Workflow loses Capacity and Priority Review · Improvement Handoff.

downstream · hop 2

Open process

Operate and Improve a Process

Trigger · Policy and operating mechanisms receive operational acceptance.

Carries · Active Policy Version · Operational Acceptance

If Implement and transition the policy is skipped, Operate and Improve a Process loses Active Policy Version · Operational Acceptance.

downstream · hop 2

Open process

Review Manager-System Health

Trigger · The diagnosis identifies work or process design as a material cause.

Carries · Improvement Handoff

If the handoff from Review Manager-System Health is skipped, Redesign Work and Workflow loses Improvement Handoff.

downstream · hop 2

Open process

Select a Business System

Trigger · The roadmap authorizes technology selection.

Carries · Technical Capability Charter · Target System Architecture

If Architect components and interfaces is skipped, Select a Business System loses Technical Capability Charter · Target System Architecture.

Roles

Lock method owner

Owns the research decision, evidence threshold, review gate, and transfer to synthesis.

Process evidence analyst

Discovers, retrieves, normalizes, compares, and packages evidence with provenance.

Process architect

Frames the process problem and converts accepted evidence into original Lock design.

Upstream system owner

Maintains source identity, canonical exports, access, and upstream truth.

Qualified reviewer

Reviews transfer, consequence, rights, and regulated or professional boundaries when required.

Systems + Data

Data object

Process Evidence Request

Defines why and where evidence is needed.

System of record · Lock process repository

Data object

Upstream Evidence Inventory

Records reusable material and access gaps without duplicating source identity.

System of record · Lock evidence registry linked to upstream systems

Data object

Process Evidence Packet

Provides a versioned, reviewed basis for Lock synthesis.

System of record · Lock evidence registry

Corpus Library lookup

Required

Resolves stable source and bibliographic identity.

CanonicAI canonical export

Required

Provides normalized source-derived process candidates when available.

Book Profile and Bicycle Guide retrieval

Required

Provides cross-source synthesis, terminology, tools, and source mappings.

Lock evidence and process repository

Required

Stores requests, packets, provenance, review state, and synthesis handoffs.

Measures

outcome

Decision coverage

Did the packet provide enough evidence to make the intended synthesis decision?

Accepted packets that support the stated decision divided by completed packets, with return reasons.

Monthly

quality

Traceability completeness

Can material candidate claims be traced to stable sources and permitted use?

Material candidate claims with source identity, locator, version, rights, and mapping divided by all material candidate claims.

Per packet

cycle-time

Discovery cycle time

How long does an evidence request take from approval to disposition?

Elapsed time by process family, consequence tier, and disposition.

Monthly

adoption

Canonical material reuse

Are existing canonical extracts and guides reused before original-source work?

Eligible requests using relevant CanonicAI or Bicycle material before new extraction divided by eligible requests.

Quarterly

exceptions

Unresolved evidence gaps

Which material evidence gaps remain unresolved or repeatedly recur?

Open gaps by process family, consequence, upstream system, age, and disposition.

Monthly

guardrail

Rights and attribution incidents

Did discovery preserve rights, confidentiality, and attribution boundaries?

Confirmed or suspected rights, excerpt, confidentiality, identity, or attribution failures.

Per packet and quarterly

Evidence + judgment

Lock cross-project evidence contract

lock-judgment

Lock operating rule: reuse upstream identity and canonical outputs through stable contracts rather than creating another corpus.

lock · cross-project-contracts · docs/CROSS-PROJECT-CONTRACTS.md

Lock evidence-to-standard method

lock-judgment

Lock judgment: evidence informs a reviewed original synthesis; it is not itself the standard.

lock · lock-method · docs/LOCK-METHOD.md

Draft internal method process. Validate against actual Corpus Library, CanonicAI, Book Profile, and Bicycle Guide export contracts before automating retrieval.