← Catalogue
World Models · legacy example

Practice Method & Procedure

This meta-model describes codified ways of doing things: methods (the reasoned approach), procedures (the step-by-step instructions), the standards they implement, and the competences they demand. It is separate from process (K3) because a method is knowledge, published, versioned and adopted, whereas a process is an operationalized flow; many processes across many organizations can codify the same method.

AI YAMLAGENTS.mdSource
IDworld.k6-practice-method-and-procedure
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainactivity-work
Tagspractice, method, procedure
Data structure

Bundles and layers

Bundle

codification

The documented way itself

Layers

methodDefinition`: approach, principles and rationale · `procedureText`: ordered step instructions · `standardReference`: external norms the method implements

Bundle

applicability

Where and by whom it may be used

Layers

competenceRequirement`: capabilities a practitioner needs · `scopeOfUse`: domains, conditions and limits of applicability

Bundle

lifecycle

Currency and uptake

Layers

versioning`: editions, supersession and errata · `adoption`: who adopted which edition and attested conformity

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.functionAndCapability` (K1): competence requirements resolve to capabilities and proficiency levels
  • REFERENCE `world.organization` (O1): authoring and adopting organizations
  • REFERENCE `world.processAndWorkflow` (K3): processes operationalize methods; the link is held on the process side and navigable from here
  • imports: iso-management-systems (REFERENCE): management system requirements that methods commonly implement
  • imports: iso-9001 (ALIGN): quality management vocabulary for procedures and conformity

Canon, patches & standards

  • REFERENCE `world.functionAndCapability` (K1): competence requirements resolve to capabilities and proficiency levels
  • REFERENCE `world.organization` (O1): authoring and adopting organizations
  • REFERENCE `world.processAndWorkflow` (K3): processes operationalize methods; the link is held on the process side and navigable from here
  • imports: iso-management-systems (REFERENCE): management system requirements that methods commonly implement
  • imports: iso-9001 (ALIGN): quality management vocabulary for procedures and conformity

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `methodAccess`: a consumer obtains the right to read and apply a method, free or licensed, per the author's terms
  • `adoptionAttestation`: an adopter declares conformity to an edition, verifiable by third parties
  • `revisionSubscription`: an adopter receives notice of new editions, errata and deprecations

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The authoring organization owns each method and its editions; adopters own their adoption records. Reading and applying a method follows owner-granted contracts under the catalogue's ownership and access models (S1/S2), with audit via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `method`: a codified approach to a class of work; key attributes: name, purpose, principles, authoring organization, domain
  • `procedure`: step-by-step instructions realizing a method; key attributes: name, preconditions, safety notes, expected result
  • `procedureStep`: one instruction; key attributes: order, action text, inputs, checks
  • `standardReference`: an external norm implemented or cited; key attributes: standard identifier, clause, relation kind
  • `competenceRequirement`: a demanded practitioner ability; key attributes: capability reference, minimum level, certification needed
  • `edition`: a published version of a method or procedure; key attributes: version, release date, change summary, status
  • `adoptionRecord`: an organization's uptake of an edition; key attributes: adopter reference, edition, date, conformity attestation

Relationships

  • `method` -> detailedBy -> `procedure` (one-to-many): the instructions that make the approach executable
  • `procedure` -> comprises -> `procedureStep` (one-to-many): the ordered instructions
  • `method` -> implements -> `standardReference` (many-to-many): the norms the method gives effect to
  • `method` -> requires -> `competenceRequirement` (one-to-many): who is fit to apply it
  • `edition` -> supersedes -> `edition` (one-to-one): the version lineage
  • `adoptionRecord` -> adoptedBy -> `organization` (many-to-one): the organization that took the method into use

Events

  • `methodPublished`: a method was released for use by its authoring organization
  • `editionReleased`: a new version of a method or procedure was issued
  • `procedureRevised`: instructions were changed within an edition cycle
  • `methodAdopted`: an organization recorded uptake of an edition
  • `methodDeprecated`: an edition or a whole method was withdrawn from recommended use

Projections

  • `practitionerHandbook`: the current edition's procedures for daily use; omits history and adoption data
  • `complianceMatrix`: methods mapped to the standard clauses they implement; omits procedure text
  • `trainingSyllabus`: competence requirements and steps shaped for instruction; omits versioning detail