19_STACK_W/TESTS_STACK

Bytes: 8233 | SHA-256: 42b6f509977d7f1a95201e0d2a05abe5a739bba01b2546afb5b5bd779ef8d785 | Source: 19_STACK_W/TESTS_STACK_W.md

Page Sections

# Stack W numbered integration tests line 1
strictly non-runtime Stack W family. line 10
## 1. Invocation and exit contract line 12
From the repository root: line 14
Compact output: line 20
or regression assertion failed. line 29
Every run emits: line 31
## 2. Exact base and candidate immutability line 45
The gate pins all of the following rather than accepting branch recency: line 47
is intentionally not called from this line 64
cumulative branch. Its W-03 containment law correctly rejects additions line 65
instead proves that its whole qualification subtree remains the exact Git tree line 67
recorded above. line 68
## 3. Exact W-04 pathset line 70
must agree on exactly thirty-two changed paths: line 73
## 4. Lifecycle binding and registration map line 84
The global and local indexes must resolve exactly these IDs and targets: line 99
a global provider. line 114
## 5. Nineteen-file mutation replay line 116
nineteen source/target pairs: line 119
For each pair the gate verifies: line 126
4. in-memory ordered replacement ending byte-for-byte equal to the line 134
6. operation classes and their union contained in the HP-030:A envelope: line 137
8. no JSON-pointer claim on Markdown successors. line 143
The eleven W-04-only control files are listed separately and cannot be counted line 145
as semantic successor replay evidence. line 146
## 6. Topology, bindings, profiles, and fixtures line 148
The numbered JSON corpus must preserve: line 150
The three qualified-data schemas and three W-04 control schemas must parse and line 161
retain their exact Draft 2020-12 schema identities. All changed JSON must parse line 162
as strict UTF-8. line 163
## 7. Runtime prohibition line 165
Registration exposes identity and location only. The validator rejects: line 167
or main. line 180
## 8. Regression boundary line 182
The W gate also rejects unresolved conflict markers across all thirty-two line 190
authorized paths. line 191
## 9. Interpretation line 193
promotion. line 198

# Stack W numbered integration tests Version: `1.0.0-W-NUMBERED-INTEGRATION-TESTS` Status: `CANONICAL SUPPORT / NON_PROVIDER / NON_RUNTIME / RUNTIME_DISABLED` Official title: `REGIMEN W — HABITUS MORALES / MORAL HABITS` Scope: deterministic validation of the HP-030:A numbered, registered, and strictly non-runtime Stack W family. ## 1. Invocation and exit contract From the repository root: ```powershell powershell -NoProfile -ExecutionPolicy Bypass -File "AGLA_ArsGeneralisLlullApplied\19_STACK_W\VALIDATE_STACK_W.ps1" ``` Compact output: ```powershell powershell -NoProfile -ExecutionPolicy Bypass -File "AGLA_ArsGeneralisLlullApplied\19_STACK_W\VALIDATE_STACK_W.ps1" -Quiet ``` The validator is offline and read-only. Exit `0` means every W-04 assertion and all three required regressions passed. Exit `1` means at least one exact base, path, hash, binding, topology, registration, lifecycle, runtime, parse, or regression assertion failed. Every run emits: ```text STACK_W_NUMBERED_CHECKS_PASSED=<integer> STACK_W_NUMBERED_FAILURE_COUNT=<integer> STACK_W_NUMBERED_INTEGRATION_READINESS=READY|FAIL EXECUTION_BASE=58ce4cec5f15a78b0263e85deea5a1e9e7412eed QUALIFICATION_SUBTREE=f9894202d45a94aab488d0919606b431d001cdea CANDIDATE_PROVENANCE=IMMUTABLE NUMBERED_LIFECYCLE=CANONICAL_SOURCE_AND_SUPPORT_NON_RUNTIME RUNTIME_POSTURE=RUNTIME_DISABLED AUTHORITY_EFFECT=NO_RUNTIME_AUTHORITY ``` ## 2. Exact base and candidate immutability The gate pins all of the following rather than accepting branch recency: - execution commit `58ce4cec5f15a78b0263e85deea5a1e9e7412eed`; - root tree `564560ebf3a767ee39bd1267fdfc862f950d2d0c`; - qualification subtree `f9894202d45a94aab488d0919606b431d001cdea`; - qualification fidelity-manifest blob `e668e92a7b2e094344a6cf04d2202ffed150ee5b`; - qualification-report blob `8c6ccd2dd139a6162a35e224490d573d4721b326`; - the recorded W-03 result `71 PASS / 0 FAIL / 0 BLOCK / exit 0`. The complete candidate and qualification lane must have no tracked, staged, committed, or untracked W-04 delta. `../_01_INTEGRATION_CANDIDATES/STACK_W/QUALIFICATION/VALIDATE_STACK_W_CANDIDATE.ps1` is intentionally not called from this cumulative branch. Its W-03 containment law correctly rejects additions outside `QUALIFICATION/`. W-03 is replayed only at the exact base commit; W-04 instead proves that its whole qualification subtree remains the exact Git tree recorded above. ## 3. Exact W-04 pathset `INTEGRATION/W_PATHSET_MANIFEST.json` and a separate hard-coded validator map must agree on exactly thirty-two changed paths: - twenty-eight additions under `19_STACK_W`; - exactly two W LIBER additions under `90_STACK_LIBER`; - one modification to `SYSTEM_INDEX_CURRENT.md`; - one modification to `STRUCTURE_REPORT.md`. The validator rejects a missing path, an extra path, a wrong add/modify classification, any W-04 delta under `17_STACK_NOTAE` or `18_STACK_MACHINA`, and any third change under `90_STACK_LIBER`. ## 4. Lifecycle binding and registration map `INTEGRATION/W_NUMBERED_LIFECYCLE_BINDING_RECORD.json` must bind exactly `HP-030: A` to: - v1.0.0 at `19_STACK_W`; - five classes and ALIAS as `CANONICAL_SOURCE_NON_RUNTIME_RUNTIME_DISABLED`; - internal support as `CANONICAL_SUPPORT_NON_PROVIDER_NON_RUNTIME_RUNTIME_DISABLED`; - two LIBER objects as `CANONICAL_SUPPORT_NON_INFORMANT_NON_PROVIDER_NON_RUNTIME_RUNTIME_DISABLED`; - `runtime_binding: DISABLED` and `REGISTERED_IDENTITY_ONLY_NOT_ADMITTED`. The global and local indexes must resolve exactly these IDs and targets: | ID | Target | Role | |---|---|---| | `IDX-W-TENET` | `19_STACK_W/TENET_W_DoctrinalInvariants.md` | identity/discovery only | | `IDX-W-ROTA` | `19_STACK_W/ROTAS_W_StructuralInstantiation.md` | identity/discovery only | | `IDX-W-AREPO` | `19_STACK_W/AREPO_W_InputAdmissibility.md` | identity/discovery only | | `IDX-W-OPERA` | `19_STACK_W/OPERA_W_ExecutionMechanism.md` | identity/discovery only; not executable | | `IDX-W-SATOR` | `19_STACK_W/SATOR_W_OutputRequirements.md` | identity/discovery only | | `IDX-W-ALIAS` | `19_STACK_W/ALIAS_W.json` | identity/discovery only | | `IDX-W-DEP` | `19_STACK_W/DEP_W_DependencyRecord.md` | discovery; non-provider | | `IDX-LIBER-W-SOURCE-SUBSTRATE` | `90_STACK_LIBER/LIBER_X_W_SOURCE_AND_STRUCTURAL_SUBSTRATE.md` | discovery; non-provider; non-informant | | `IDX-LIBER-W-EVACUATIO-PROOF` | `90_STACK_LIBER/LIBER_X_W_EX_EVACUATIO_STRUCTURAL_PROOF.md` | discovery; non-provider; non-informant | No matrix, profile, fixture, schema, report, or integration-control artifact is a global provider. ## 5. Nineteen-file mutation replay `INTEGRATION/W_NUMBERED_SUCCESSOR_AND_MUTATION_MANIFEST.json` contains exactly nineteen source/target pairs: - ten qualified source-family successors, including the two LIBER targets; - nine qualified supports: profile dataset, human bindings, positive and adverse fixtures, three schemas, lexical/title decision, and rotation decision. For each pair the gate verifies: 1. exact artifact order and exact source path at the pinned base; 2. raw source bytes read directly from the exact Git blob OID, with strict UTF-8/no-BOM decoding and pinned SHA-256; 3. a contiguous operation sequence `1..N`, each with a base64 UTF-8 preimage/postimage, exactly one ordinal preimage occurrence, and whole-file pre/post SHA-256 chain; 4. in-memory ordered replacement ending byte-for-byte equal to the LF-normalized UTF-8 target and its recorded SHA-256; 5. exact target path, v1.0.0 lifecycle, and disabled runtime; 6. operation classes and their union contained in the HP-030:A envelope: `VERSION`, `STATUS_LIFECYCLE`, `NUMBERED_PATH`, `INTERNAL_REFERENCE`, `REGISTRY_METADATA`, and `PROVENANCE_METADATA`; 7. for JSON successors, an independently parsed source/target pointer diff equal to the recorded allowlist, with every pointer inside an artifact- specific lifecycle/path/reference/registry/provenance whitelist; 8. no JSON-pointer claim on Markdown successors. The eleven W-04-only control files are listed separately and cannot be counted as semantic successor replay evidence. ## 6. Topology, bindings, profiles, and fixtures The numbered JSON corpus must preserve: - carrier order `B C D E F G H I K`; - thirty-six unique signed V/U addresses; - reciprocal counterpart and semantic-identity references; - thirty-six unique A/T profile records; - the exact dependency-safe order and selected options of HP-019 through HP-023 and HP-026 through HP-029; - ten positive plus forty adverse unique fixtures; - `runtime_execution_allowed: false` for every fixture. The three qualified-data schemas and three W-04 control schemas must parse and retain their exact Draft 2020-12 schema identities. All changed JSON must parse as strict UTF-8. ## 7. Runtime prohibition Registration exposes identity and location only. The validator rejects: - `runtime_available: true`; - `RUNTIME_ENABLED` or `RUNTIME_ACTIVE` tokens; - enabled or active `runtime_binding` fields; - a class or ALIAS without exact canonical-source/non-runtime status; - DEP without non-provider status; - either LIBER without non-informant, non-provider, and runtime-disabled status; - an OPERA index record lacking `NOT_EXECUTABLE`. Canonical source status does not satisfy AREPO, create an invocation, execute OPERA W, authorize MACHINA or Sigma, modify deployment, or promote development or main. ## 8. Regression boundary Every full run executes and requires exit `0` from: - `00_ROOT_CLASS_LAWS/VALIDATE_FIVE_CLASS_OPERA_REENTRY_INVARIANT.ps1`; - `15_STACK_LLULLIANA/VALIDATE_LLULLIANA.ps1 -Quiet`; - `16_STACK_ARITHMETICA/VALIDATE_ARITHMETICA.ps1 -Quiet`. The W gate also rejects unresolved conflict markers across all thirty-two authorized paths. ## 9. Interpretation A `READY` result means only that the exact HP-030:A non-runtime numbered slice is mechanically coherent and regression-safe. It does not grant runtime, deployment, MACHINA, Sigma, G/SK repair, development promotion, or main promotion.