{
  "vercy": "1.0-draft",
  "publication": {
    "status": "research-draft",
    "adjudicationStatus": "unreviewed",
    "publishableCanonical": false,
    "generatedAt": "2026-09-13T20:31:57Z",
    "providers": [
      "Claude"
    ],
    "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify",
    "pass": 2,
    "wave": 4,
    "engine": "claude",
    "enrichment": {
      "pass": 3,
      "engine": "claude",
      "producedAt": "2026-10-06T12:00:00Z",
      "ingestedAt": "2026-10-06T07:34:50+00:00",
      "fields": [
        "agent_conduct",
        "ethics",
        "owners"
      ]
    },
    "gate": {
      "passed": true,
      "version": "1.0",
      "at": "2026-10-06T19:51:56+00:00",
      "evidence": [
        "completeness 1.00",
        "sense: Wikidata description",
        "2 live sources",
        "review by codex: pass"
      ]
    }
  },
  "metaModel": {
    "id": "THING-Q2101564",
    "registryId": "vr.tr.specification",
    "name": "specification",
    "version": "0.2.0-wave.4",
    "entryKind": "thing",
    "family": "Thing Registry",
    "domain": [
      "INF.MED"
    ],
    "status": "research-draft"
  },
  "canonicalUrl": "https://ver.cy/models/thing/q2101564/",
  "model": {
    "registry_id": "vr.tr.specification",
    "name": "specification",
    "purpose": "Let an agent explain specifications, relay kinds, structure and relationship to standards from standards bodies and engineering sources, describe the named specification types, and distinguish specifications from standards, requirements documents, contracts and sampling plans.",
    "definition": "A document that precisely states requirements, design, behaviour or characteristics that a product, material, process, service or data format must meet, used in engineering, software, procurement and standardisation, in forms such as technical specifications, open specifications freely available for implementation, Publicly Available Specifications published by BSI, Java Specification Requests in the Java Community Process and record layouts describing data file structures; the registry alias sampling plan is a quality control scheme that may be part of a specification but is a different document type.",
    "what_it_is_for": "Defining what something must be or do.",
    "affordances": [
      "explain kinds and structure",
      "relay relationship to standards",
      "describe named specification types",
      "distinguish related documents"
    ],
    "distinguishing_features": [
      "Precise requirements",
      "Verifiable",
      "Many domains",
      "May be open or proprietary"
    ],
    "appearance": "Not a visible object; structured documents with numbered requirements.",
    "visual_identification": [
      "Document stating precise requirements",
      "Java Specification Request, technical specification, open specification, sampling plan, record layout, Publicly Available Specification",
      "Standards are consensus documents from recognised bodies; requirements documents may be informal; contracts create obligations; sampling plans guide inspection"
    ],
    "physical_properties": [
      {
        "quantity": "ISO/IEC Directives document types",
        "typical_range": "IS, TS, PAS, TR",
        "unit": "list",
        "note": ""
      },
      {
        "quantity": "Java Community Process",
        "typical_range": "1998",
        "unit": "year",
        "note": ""
      },
      {
        "quantity": "RFC 2119 keywords",
        "typical_range": "MUST, SHOULD, MAY",
        "unit": "note",
        "note": ""
      }
    ],
    "families_and_kinds": [
      "technical specifications",
      "open specifications",
      "publicly available specifications",
      "software and API specifications",
      "data format and record layout specifications",
      "procurement specifications"
    ],
    "related_models": [
      {
        "relation": "is a kind of",
        "target": "document",
        "why": "in registry terms"
      },
      {
        "relation": "is contrasted with",
        "target": "technical standard",
        "why": ""
      },
      {
        "relation": "includes",
        "target": "Java Specification Request",
        "why": ""
      },
      {
        "relation": "is contrasted with",
        "target": "acceptance sampling",
        "why": "misfiled alias sampling plan"
      }
    ],
    "identifiers": [],
    "standards_and_regulation": [
      "ISO/IEC Directives",
      "RFC 2119 and RFC 8174",
      "Public procurement rules on technical specifications"
    ],
    "failure_modes_and_hazards": [
      "Ambiguous requirements",
      "Confusing specifications with standards",
      "Registry alias for a sampling plan"
    ],
    "in_scope": [],
    "out_of_scope": [],
    "characteristics": [],
    "agent_conduct": {
      "may": [
        "Check a design, product or dataset against a specification and report any gaps.",
        "Cite a specification by its title, version and issuer."
      ],
      "must_not": [
        "Claim that something meets a specification without testing it.",
        "Change a shared specification without its owner's approval.",
        "Present a private specification as an official standard.",
        "Copy or circulate a confidential specification beyond its audience."
      ],
      "requires_human": [
        "Accepting deviations from a specification in safety-relevant work."
      ]
    },
    "ethics": {
      "considerations": [
        "Ambiguous specifications shift risk onto the people who build and use the product.",
        "Specifications can be written to favour one supplier in public procurement."
      ],
      "affected_parties": [
        "Users of the product",
        "Suppliers and bidders",
        "Engineers"
      ]
    },
    "owners": {
      "steward": "The author or issuing organization of the specification.",
      "master_systems": []
    }
  },
  "sources": [
    {
      "id": "wikidata",
      "title": "Wikidata item Q2101564: specification",
      "url": "https://www.wikidata.org/wiki/Q2101564",
      "url_status": "live",
      "what_it_supports": "identity and sense of the item",
      "checked_by": "wikidata-api"
    },
    {
      "id": "wikipedia-en",
      "title": "Wikipedia: Specification (technical standard)",
      "url": "https://en.wikipedia.org/wiki/Specification_%28technical_standard%29",
      "url_status": "live",
      "what_it_supports": "general description of the item",
      "checked_by": "wikidata-api sitelink"
    }
  ],
  "structure": {
    "bundles": [
      {
        "id": "understand",
        "name": "Understand",
        "description": "What a specification is.",
        "rationale": "Definition.",
        "layers": [
          {
            "id": "definition",
            "name": "Definition",
            "description": "Definition.",
            "findings": [
              {
                "id": "definition-finding",
                "name": "Definition",
                "description": "Definition.",
                "questions": [
                  {
                    "text": "What is a specification, and how does it differ from standards, requirements documents, contracts and sampling plans?",
                    "kind": "definition"
                  },
                  {
                    "text": "Is the question about software, engineering, procurement or standards?",
                    "kind": "boundary"
                  }
                ]
              }
            ]
          },
          {
            "id": "types",
            "name": "Types",
            "description": "Named types.",
            "findings": [
              {
                "id": "types-finding",
                "name": "Types",
                "description": "Types.",
                "questions": [
                  {
                    "text": "What are JSRs, technical specifications, open specifications, record layouts and PAS documents, and why is a sampling plan different?",
                    "kind": "definition"
                  },
                  {
                    "text": "Which entry fits the specific type?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "writing",
        "name": "Writing",
        "description": "Writing specifications.",
        "rationale": "Sources.",
        "layers": [
          {
            "id": "language",
            "name": "Language",
            "description": "Requirement language.",
            "findings": [
              {
                "id": "language-finding",
                "name": "Language",
                "description": "Language.",
                "questions": [
                  {
                    "text": "How do keywords such as MUST and SHOULD make requirements testable?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which references are standard?",
                    "kind": "provenance"
                  }
                ]
              }
            ]
          },
          {
            "id": "structure",
            "name": "Structure",
            "description": "Structure.",
            "findings": [
              {
                "id": "structure-finding",
                "name": "Structure",
                "description": "Structure.",
                "questions": [
                  {
                    "text": "What sections do specifications typically contain?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which sources are cited?",
                    "kind": "provenance"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "standards",
        "name": "Standards",
        "description": "Standards processes.",
        "rationale": "Regulation.",
        "layers": [
          {
            "id": "iso",
            "name": "ISO",
            "description": "ISO document types.",
            "findings": [
              {
                "id": "iso-finding",
                "name": "ISO",
                "description": "ISO.",
                "questions": [
                  {
                    "text": "How do ISO technical specifications differ from International Standards?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits International Organization for Standardization?",
                    "kind": "action"
                  }
                ]
              }
            ]
          },
          {
            "id": "open",
            "name": "Open",
            "description": "Open specifications.",
            "findings": [
              {
                "id": "open-finding",
                "name": "Open",
                "description": "Open.",
                "questions": [
                  {
                    "text": "What makes a specification open, and how are community processes like the JCP run?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits open standard?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "context",
        "name": "Context",
        "description": "Uses.",
        "rationale": "Context.",
        "layers": [
          {
            "id": "procurement",
            "name": "Procurement",
            "description": "Procurement.",
            "findings": [
              {
                "id": "procurement-finding",
                "name": "Procurement",
                "description": "Procurement.",
                "questions": [
                  {
                    "text": "How are specifications used in public procurement?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits public procurement?",
                    "kind": "action"
                  }
                ]
              }
            ]
          },
          {
            "id": "data",
            "name": "Data",
            "description": "Data layouts.",
            "findings": [
              {
                "id": "data-finding",
                "name": "Data",
                "description": "Data.",
                "questions": [
                  {
                    "text": "How do record layouts describe fixed-width data files?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits file format?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      }
    ]
  },
  "openQuestions": [
    "Should PAS and JSR be separate entries?",
    "How should standards bodies be linked?",
    "The registry alias sampling plan should be moved to acceptance sampling"
  ],
  "statistics": {
    "bundles": 4,
    "layers": 8,
    "findings": 8,
    "questions": 16
  }
}