Distillation

🔴 (22:58) User directed that Terraform detector order must always remain exactly: 1. detectGitHub; 2. detectGit; 3. detectBitBucket; 4. detectGCS; 5. detectS3; 6. detectAbsFilePath. detectAbsFilePath must remain the final fallback because it claims every nonempty input and would prevent later detectors from running if placed earlier; shorthand detectors must not be added, and new source types must use canonical source-address syntax. 🔴 (22:58) User directed that open, rejected, or unmerged proposals must never be treated as effective changes. 🔴 (22:58) User’s license-adjudication convention is to scope the merged Terraform Habitat/Chef EULA change only to enforcement proven for Terraform’s Habitat provisioner; ground findings in exact body, patch, documentation, and merge-metadata evidence, including accept_license validation and HAB_LICENSE=accept; do not infer the effective date of Chef Software’s underlying EULA policy or attribute organizational authority, ownership, or rights to Chef without direct evidence; keep announcement dates distinct from effective implementation dates. 🟡 (22:55) Inspection of src/institution_lab/governance_coding.py lines 241–315 found that validate_response() requires exact top-level RESPONSE_KEYS; validates record_class, event_kind, nonempty nullable title/affected_scope/ambiguity, ISO-or-null announced_on/effective_on, allowed body_patch_relation, and finite numeric confidence in [0,1]. 🟡 (22:55) validate_response() requires power_changes to be an array. Each edge must have exactly POWER_KEYS; nonempty actor, target, and scope; allowed right_kind, direction, and change_status; and a nonempty evidence_refs array whose entries exactly match REF_KEYS and contain a nonempty quote occurring verbatim in the referenced document source. 🟡 (22:55) validate_response() defines institutional classes as effective_institutional_change, announced_institutional_change, and proposal_only; these classes require at least one power_changes edge, while non-institutional records must contain no edges. abstain requires a non-null ambiguity. 🟡 (22:55) Inspection of src/institution_lab/governance_coding.py lines 318–374 found that _validate_run() requires a nonempty document list, one unique raw response per document with an exact record-ID set match, matching coding_id, coding_schema_sha256, run_id, source_url, MODEL_INPUT_FIELDS, model, and reasoning_effort, plus a nonnegative integer elapsed_ms; it parses response_text through parse_response() and stores response, schema_valid, validation_errors, model, reasoning_effort, and elapsed_ms. 🟡 (22:55) Inspection of src/institution_lab/governance_coding.py lines 377–405 found that _edge_signature() canonicalizes each power_changes edge from actor, right_kind, target, direction, change_status, scope, and sorted (source_id, quote) evidence-reference pairs, then returns the sorted edge tuples. 🟡 (22:56) Assistant determined that the fragment validator adds semantic gates beyond JSON Schema: institutional/proposal classes always require at least one edge; accepted codings must exactly equal a schema-valid frozen response; and graph diffs are derived from the named valid response. 🟡 (22:56) Assistant adopted the review rule that truncated patch selection remains an unresolved evidence limitation unless retained frozen sources independently prove a narrower conclusion. 🟡 (22:57) The five Terraform documents occur in this frozen order in cases/review/oss-governance-adjudication-v1/documents.json: 1. terraform-github-pr-21175; 2. terraform-github-pr-22745; 3. terraform-github-pr-33661; 4. terraform-github-pr-34847; 5. terraform-github-pr-38385. 🟡 (22:57) Review workflow state: 1. “Inspect current adjudication schema, fragment validator, and OpenTofu exemplar shape” — completed, high priority; 2. “Re-audit the five frozen Terraform documents in document order” — in progress, high priority; 3. “Inspect only the five records' direct frozen responses after source audit” — pending, high priority; 4. “Construct and validate the complete subset C fragment in memory” — pending, high priority. 🟡 (22:58) Relevant adjudication inputs located at cases/review/oss-governance-adjudication-v1/documents.json, cases/review/oss-governance-adjudication-v1/v1.2-coding-package.json, cases/review/oss-governance-adjudication-v1/artifact-9642983578.zip, and exemplar cases/review/oss-governance-adjudication-v1/fragments/opentofu-a2.json.