-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathQWEN.html
More file actions
1620 lines (1618 loc) · 87.1 KB
/
QWEN.html
File metadata and controls
1620 lines (1618 loc) · 87.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>QWEN</title>
<style>
html {
color: #1a1a1a;
background-color: #fdfdfd;
}
body {
margin: 0 auto;
max-width: 36em;
padding-left: 50px;
padding-right: 50px;
padding-top: 50px;
padding-bottom: 50px;
hyphens: auto;
overflow-wrap: break-word;
text-rendering: optimizeLegibility;
font-kerning: normal;
}
@media (max-width: 600px) {
body {
font-size: 0.9em;
padding: 12px;
}
h1 {
font-size: 1.8em;
}
}
@media print {
html {
background-color: white;
}
body {
background-color: transparent;
color: black;
font-size: 12pt;
}
p, h2, h3 {
orphans: 3;
widows: 3;
}
h2, h3, h4 {
page-break-after: avoid;
}
}
p {
margin: 1em 0;
}
a {
color: #1a1a1a;
}
a:visited {
color: #1a1a1a;
}
img {
max-width: 100%;
}
svg {
height: auto;
max-width: 100%;
}
h1, h2, h3, h4, h5, h6 {
margin-top: 1.4em;
}
h5, h6 {
font-size: 1em;
font-style: italic;
}
h6 {
font-weight: normal;
}
ol, ul {
padding-left: 1.7em;
margin-top: 1em;
}
li > ol, li > ul {
margin-top: 0;
}
blockquote {
margin: 1em 0 1em 1.7em;
padding-left: 1em;
border-left: 2px solid #e6e6e6;
color: #606060;
}
code {
font-family: Menlo, Monaco, Consolas, 'Lucida Console', monospace;
font-size: 85%;
margin: 0;
hyphens: manual;
}
pre {
margin: 1em 0;
overflow: auto;
}
pre code {
padding: 0;
overflow: visible;
overflow-wrap: normal;
}
.sourceCode {
background-color: transparent;
overflow: visible;
}
hr {
border: none;
border-top: 1px solid #1a1a1a;
height: 1px;
margin: 1em 0;
}
table {
margin: 1em 0;
border-collapse: collapse;
width: 100%;
overflow-x: auto;
display: block;
font-variant-numeric: lining-nums tabular-nums;
}
table caption {
margin-bottom: 0.75em;
}
tbody {
margin-top: 0.5em;
border-top: 1px solid #1a1a1a;
border-bottom: 1px solid #1a1a1a;
}
th {
border-top: 1px solid #1a1a1a;
padding: 0.25em 0.5em 0.25em 0.5em;
}
td {
padding: 0.125em 0.5em 0.25em 0.5em;
}
header {
margin-bottom: 4em;
text-align: center;
}
#TOC li {
list-style: none;
}
#TOC ul {
padding-left: 1.3em;
}
#TOC > ul {
padding-left: 0;
}
#TOC a:not(:hover) {
text-decoration: none;
}
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
div.columns{display: flex; gap: min(4vw, 1.5em);}
div.column{flex: auto; overflow-x: auto;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list[class]{list-style: none;}
ul.task-list li input[type="checkbox"] {
font-size: inherit;
width: 0.8em;
margin: 0 0.8em 0.2em -1.6em;
vertical-align: middle;
}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
</head>
<body>
<header id="title-block-header">
<h1 class="title">QWEN</h1>
</header>
<h1 id="qwenmd--helixqa-docprocessor">QWEN.md — HelixQA
DocProcessor</h1>
<table>
<thead>
<tr>
<th>Field</th>
<th>Value</th>
</tr>
</thead>
<tbody>
<tr>
<td>Revision</td>
<td>1</td>
</tr>
<tr>
<td>Created</td>
<td>2026-05-23</td>
</tr>
<tr>
<td>Last modified</td>
<td>2026-05-23</td>
</tr>
<tr>
<td>Status</td>
<td>active</td>
</tr>
<tr>
<td>Status summary</td>
<td>Created per Phase 39.IT (User mandate 2026-05-23) — propagation of
QWEN.md across the consumer fleet, mirroring CLAUDE.md + AGENTS.md per
§11.4.35 canonical-root inheritance.</td>
</tr>
<tr>
<td>Issues</td>
<td>none</td>
</tr>
<tr>
<td>Continuation</td>
<td>—</td>
</tr>
</tbody>
</table>
<h2 id="inherited-from-constitutionqwenmd">INHERITED FROM
constitution/QWEN.md</h2>
<p>All rules in <code>constitution/QWEN.md</code> (and the
<code>constitution/Constitution.md</code> it references) apply
unconditionally. This module's rules below extend them — they do NOT
weaken any universal clause. When this file disagrees with the
constitution submodule, the constitution wins. Locate the constitution
submodule from any arbitrary nested depth using its
<code>find_constitution.sh</code> helper.</p>
<p>The universal anti-bluff covenant (§11.4), no-guessing mandate
(§11.4.6), credentials-handling mandate (§11.4.10), host-session safety
(§12 + §12.6 + §12.10), and data safety (§9) all live in
<code>constitution/Constitution.md</code>. Read it before working on any
non-trivial change.</p>
<p>@constitution/QWEN.md</p>
<p>Canonical reference: <a href="https://github.com/HelixDevelopment/HelixConstitution">https://github.com/HelixDevelopment/HelixConstitution</a></p>
<h2 id="how-this-file-relates-to-claudemd--agentsmd">How this file
relates to CLAUDE.md + AGENTS.md</h2>
<p>Per §11.4.35 canonical-root inheritance clarity:</p>
<ul>
<li><code>constitution/QWEN.md</code> is the universal canonical root
for the Qwen Code CLI.</li>
<li>This file is the consumer-side extension for this submodule,
carrying only the inheritance pointer + the §11.4 covenant anchors + a
brief module summary.</li>
<li>The full module ruleset lives in this submodule's sibling
<code>CLAUDE.md</code>. Qwen Code agents MUST read CLAUDE.md before
performing any work; this QWEN.md is the Qwen-specific entry point that
ensures Qwen reads the inheritance pointer + anti-bluff covenant on
every session.</li>
</ul>
<h2 id="module-summary">Module summary</h2>
<p>Document-processing pipeline for HelixQA. Decomposes specifications,
requirements, and reference documentation into structured forms
consumable by Challenges and the LLM orchestration layer.</p>
<p>For full module context (build steps, integration points,
host-session safety, submodule-specific commit/push discipline) read
this directory's <code>CLAUDE.md</code> and <code>AGENTS.md</code>.</p>
<h2 id="mandatory-anti-bluff-covenant--end-user-quality-guarantee-user-mandate-2026-04-28">MANDATORY
ANTI-BLUFF COVENANT — END-USER QUALITY GUARANTEE (User mandate,
2026-04-28)</h2>
<p><strong>Forensic anchor — direct user mandate
(verbatim):</strong></p>
<blockquote>
<p>"We had been in position that all tests do execute with success and
all Challenges as well, but in reality the most of the features does not
work and can't be used! This MUST NOT be the case and execution of tests
and Challenges MUST guarantee the quality, the completion and full
usability by end users of the product!"</p>
</blockquote>
<p>This is the historical origin of the project's anti-bluff covenant.
Every test, every Challenge, every gate, every mutation pair exists to
make the failure mode (PASS on broken-for-end-user feature) mechanically
impossible.</p>
<p><strong>Operative rule:</strong> the bar for shipping is
<strong>not</strong> "tests pass" but <strong>"users can use the
feature."</strong> Every PASS in this codebase MUST carry positive
evidence captured during execution that the feature works for the end
user. Metadata-only PASS, configuration-only PASS, "absence-of-error"
PASS, and grep-based PASS without runtime evidence are all critical
defects regardless of how green the summary line looks.</p>
<p><strong>Tests AND Challenges (HelixQA) are bound equally</strong> — a
Challenge that scores PASS on a non-functional feature is the same class
of defect as a unit test that does. Both must produce positive end-user
evidence; both are subject to the §8.1 five-constraint rule and §11
captured-evidence requirement.</p>
<p><strong>Canonical authority:</strong> constitution submodule <a href="../../../../constitution/Constitution.md"><code>Constitution.md</code></a>
§11.4 (this end-user-quality-guarantee forensic anchor — propagation
requirement enforced by pre-build gate
<code>CM-COVENANT-114-QWEN-PROPAGATION</code>).</p>
<p>Non-compliance is a release blocker regardless of context.</p>
<h2 id="anti-bluff-manner-clause-verbatim-operator-mandate--hrd-158-covenant-cascade">Anti-bluff-manner
clause (verbatim operator mandate — HRD-158 covenant cascade)</h2>
<p><strong>Forensic anchor — verbatim operator mandate:</strong></p>
<blockquote>
<p>"IMPORTANT: Make sure that all existing tests and Challenges do work
in anti-bluff manner — they MUST confirm that all tested codebase really
works as expected! execution of tests and Challenges MUST guarantee the
quality, the completition and full usability by end users of the
product! This MUST BE part of Constitution of our project, its CLAUDE.MD
and AGENTS.MD if it is not there already, and to be applied to all
Submodules's Constitution, CLAUDE.MD and AGENTS.MD as well."</p>
</blockquote>
<p>This clause is the leading verbatim operator anti-bluff mandate,
restated here for cross-file consistency with this module's CLAUDE.md /
AGENTS.md / CONSTITUTION.md. It does NOT weaken any inherited rule.
Canonical authority: constitution submodule <code>Constitution.md</code>
§11.4. Tests AND HelixQA Challenges are bound equally.</p>
<h2 id="114-extension-anchors-carried-by-this-file">§11.4 extension
anchors carried by this file</h2>
<p>The following extension anchors apply unconditionally to every change
landed in this submodule. Their full text lives in the sibling CLAUDE.md
and in the canonical <code>constitution/Constitution.md</code>. Listed
here so Qwen Code agents can locate them by literal string match:</p>
<ul>
<li><strong>§11.4.1 extension (Phase 33, 2026-05-05)</strong> —
FAIL-bluffs equally forbidden. A test that crashes for a script-internal
reason and produces a FAIL exit code is just as misleading as a
PASS-bluff. Fix at source layer, never at call sites.</li>
<li><strong>§11.4.2 extension (Phase 34, 2026-05-06)</strong> —
Recorded-evidence requirement. Every PASS for a user-visible feature
MUST be cross-checked by the analyzer against the dual-display recording
+ action timeline.</li>
<li><strong>§11.4.3 extension (Phase 34, 2026-05-06)</strong> —
Per-device-topology test dispatch. Topology-touching tests MUST detect
topology at entry and dispatch the topology-appropriate variant.</li>
<li><strong>§11.4.4 extension (User mandate, 2026-05-06)</strong> —
Test-interrupt-on-discovery + retest-from-clean-baseline. The moment any
defect is re-discovered or newly identified mid-cycle, STOP and fix at
root cause + four-layer coverage + full rebuild + reflash + retest.</li>
<li><strong>§11.4.4 expansion (User mandate, 2026-05-06)</strong> —
Systematic debugging via superpowers skills + four-layer test coverage
per fix (pre-build gate + post-build gate + post-flash on-device test +
HelixQA Challenge + paired mutation) + documentation update + no-bluff
certification per cycle.</li>
<li><strong>§11.4.5 — Audio + video quality analysis comprehensiveness
(User mandate, 2026-05-07)</strong> — Audio: presence + channel count +
sample rate + glitch census + coexistence-artifact census. Video:
presence + routing target + frame health + obstruction census +
resolution + codec. Challenges bound equally.</li>
<li><strong>§11.4.6 — No-guessing mandate (User mandate,
2026-05-08)</strong> — Forbidden vocabulary: <code>likely</code>,
<code>probably</code>, <code>maybe</code>, <code>might</code>,
<code>possibly</code>, <code>presumably</code>, <code>seems</code>,
<code>appears to</code>. Prove with captured evidence OR mark
<code>UNCONFIRMED:</code> / <code>UNKNOWN:</code> /
<code>PENDING_FORENSICS:</code>.</li>
<li><strong>§11.4.7 — Demotion-evidence rule (Phase 38.X+2 amendment,
2026-05-11)</strong> — Demotion from FAIL to lower-severity requires
positive evidence captured under the same conditions that originally
exposed the defect.</li>
<li><strong>§11.4.8 — Deep-web-research-before-implementation mandate
(User mandate, 2026-05-12)</strong> — Cite external source URL OR
literal "NO external solution found — original work" in every
non-trivial fix.</li>
<li><strong>§11.4.9 — Batch-source-fixes-before-rebuild mandate (User
mandate, 2026-05-12)</strong> — All source-side fixes that DO NOT
require runtime on-device validation MUST be landed BEFORE the next
firmware rebuild.</li>
<li><strong>§11.4.10 — Credentials-handling mandate (User mandate,
2026-05-12)</strong> — Credentials NEVER live in tracked files.
<code>.env</code> git-ignored project-wide. Tests load from
<code>scripts/testing/secrets/</code> (chmod 600).</li>
<li><strong>§11.4.13 — Out-of-band sink-side captured-evidence mandate
(User mandate, 2026-05-13)</strong> — When an HDMI sink with
network-accessible introspection API is present, every audio test MUST
consume the sink's report as captured-evidence.</li>
<li><strong>§11.4.14 — Test playback cleanup mandate (User mandate,
2026-05-13)</strong> — Every test that issues <code>am start</code> /
<code>cmd media_session play</code> MUST issue matching
<code>am force-stop</code> / <code>KEYCODE_MEDIA_STOP</code> + EXIT
trap.</li>
<li><strong>§11.4.15 — Item-status tracking mandate (User mandate,
2026-05-13)</strong> — Every active item in <code>Issues.md</code>
carries a <code>**Status:**</code> line.</li>
<li><strong>§11.4.16 — Item-type tracking mandate (User mandate,
2026-05-14)</strong> — Every active item in <code>Issues.md</code>
carries a <code>**Type:**</code> line with one of
<code>{Bug | Feature | Task}</code>.</li>
<li><strong>§11.4.40 — Full-suite retest before release tag mandate
(User mandate, 2026-05-17)</strong> — Release tag MUST NOT be created
until a complete retest with ALL existing tests has been executed on a
clean baseline.</li>
<li><strong>§11.4.41 — Pre-Force-Push Merge-First Mandate (User mandate,
2026-05-17)</strong> — Every force-push MUST be preceded by a mechanical
4-step merge-first pipeline (fetch + integrate + audit + push with
<code>--force-with-lease</code>).</li>
</ul>
<h2 id="mandatory-126-memory-budget-ceiling--60-maximum-user-mandate-2026-04-30">MANDATORY
§12.6 MEMORY-BUDGET CEILING — 60% MAXIMUM (User mandate,
2026-04-30)</h2>
<p>Project procedures MUST NOT use more than <strong>60% of total system
RAM</strong> (<code>HOST_SAFETY_MAX_MEM_PCT</code>). The remaining 40%
is reserved for the operator's other workloads. There is NO
operator-facing override flag.</p>
<p><code>scripts/build.sh</code> wraps <code>m -j</code> in
<code>bounded_run</code> so only the bounded scope is OOM-killed if the
build's collective RSS exceeds the budget —
<code>user@<uid>.service</code> stays alive.</p>
<p><strong>Canonical authority:</strong> constitution submodule <a href="../../../../constitution/Constitution.md"><code>Constitution.md</code></a>
§12.6.</p>
<p>Non-compliance is a release blocker regardless of context.</p>
<h2 id="companion-documents">Companion documents</h2>
<table>
<thead>
<tr>
<th>File</th>
<th>Role</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>CLAUDE.md</code></td>
<td>Full module ruleset (Claude Code primary context)</td>
</tr>
<tr>
<td><code>AGENTS.md</code></td>
<td>Cross-agent mirror (OpenCode, Cursor, Aider, generic AI
tooling)</td>
</tr>
<tr>
<td><code>QWEN.md</code> (this file)</td>
<td>Qwen Code CLI entry point</td>
</tr>
<tr>
<td><code>../../../../constitution/Constitution.md</code></td>
<td>Universal canonical rules</td>
</tr>
<tr>
<td><code>../../../../constitution/QWEN.md</code></td>
<td>Universal Qwen entry point</td>
</tr>
</tbody>
</table>
<h2 id="11469--universal-sink-side-positive-evidence-taxonomy--mechanical-enforcement-cascaded-from-constitution-submodule-11469">§11.4.69
— Universal Sink-Side Positive-Evidence Taxonomy + Mechanical
Enforcement (cascaded from constitution submodule §11.4.69)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-20): <em>"THIS MUST HAPPEN NEVER
AGAIN!!! We MUST HAVE this all working! Not just for audio but for every
single piece of the System!!! Proper full automation when executed with
success MUST MEAN that manual testing will be as much positive at least
regarding the success results! ... Solution MUST BE universal, generic
that solves working flows for all System components and for all future
and all existing projects! ... Everything we do MUST BE validated and
verified with rock-solid proofs and anti-bluff policy enforcement and
fulfillment!"</em></p>
</blockquote>
<p>Universal generalisation of §11.4.68 (audio-specific) across every
user-visible feature class. Every user-visible feature MUST map to one
entry in the closed-set §11.4.69 sink-side evidence taxonomy
(<code>audio_output</code>, <code>audio_input</code>,
<code>video_display</code>, <code>network_throughput</code>,
<code>network_connectivity</code>, <code>bluetooth_a2dp</code>,
<code>bluetooth_pair</code>, <code>touch_input</code>,
<code>sensor</code>, <code>gpu_render</code>, <code>storage_read</code>,
<code>storage_write</code>, <code>mediacodec_decode</code>,
<code>mediacodec_encode</code>, <code>miracast</code>,
<code>cast</code>, <code>boot_service</code>,
<code>package_install</code>, <code>permission_grant</code>,
<code>wifi_link</code>, <code>wifi_throughput</code>,
<code>ethernet_link</code>, <code>display_topology</code>,
<code>drm_playback</code>, <code>subtitle_render</code> — open to
additions, never contraction). Every PASS for a feature in the taxonomy
MUST cite a captured-evidence artefact path matching the required
evidence shape. New helper contracts (additive during grace, mandatory
after 2026-06-19):
<code>ab_pass_with_evidence <description> <evidence_path></code>
(verifies path exists + non-empty),
<code>ab_skip_with_reason <description> <closed-set-reason></code>
(reasons: <code>geo_restricted</code>, <code>operator_attended</code>,
<code>hardware_not_present</code>, <code>topology_unsupported</code>,
<code>network_unreachable_external</code>,
<code>feature_disabled_by_config</code>; forbids
<code>network_unreachable_external</code> for any taxonomy feature with
a sink-side probe); bare <code>ab_pass</code> deprecated (WARN
pre-grace, FAIL post-grace). Three pre-build gates + paired §1.1
mutations: <code>CM-SINK-EVIDENCE-PER-FEATURE</code>,
<code>CM-NO-FAIL-OPEN-SKIP</code>,
<code>CM-AB-PASS-WITH-EVIDENCE-EVERYWHERE</code>. No escape hatch — no
<code>--skip-evidence</code>, <code>--config-only-pass</code>,
<code>--allow-fail-open-skip</code>,
<code>--legacy-ab-pass-permitted</code> flag.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.69</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-69-PROPAGATION</code> enforces the anchor literal
across the consumer fleet; paired mutation strips the literal → gate
FAILs. Severity-equivalent to a §11.4 PASS-bluff at the
sink-side-evidence layer. <strong>Canonical authority:</strong>
constitution submodule <code>Constitution.md</code> §11.4.69 for the
full mandate.</p>
<h2 id="11475--mechanical-enforcement-without-exception-cascaded-from-constitution-submodule-11475">§11.4.75
— Mechanical Enforcement Without Exception (cascaded from constitution
submodule §11.4.75)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-20): <em>"Why do these violations
still happen!? This is a serious problem! We cannot rely on stability
nor consistency if we cannot respect our Constitution, mandatory rules
and constraints! Is there a way to make this always respected, followed
and applied without exception fully and unconditionally!? WE MUST HAVE
THIS WORKING FLAWLESSLY!!! Do investigate the root causes of such
problems! Once all problems are identified WE MUST apply proper
mechanisms for this not to happen NEVER EVER AGAIN!"</em></p>
</blockquote>
<p>The §11.4 covenant historically relied on agent + operator vigilance;
three 2026-05-19→20 forensic incidents proved that late-binding
enforcement fires hours-to-days after the violator commit reaches every
remote. §11.4.75 closes the gap with FIVE independent mechanical
enforcement layers — bypassing any single layer does not bypass the
discipline: (1) local <code>pre-commit</code> git hook (refuses staged
<code>.md</code> lacking sibling <code>.html</code>+<code>.pdf</code>);
(2) <code>commit_all.sh</code> integration
(<code>_constitution_sibling_check</code> +
auto-<code>sync_all_markdown_exports.sh</code> self-repair); (3) local
<code>pre-push</code> git hook (re-runs siblings + propagation-gate
subset); (4) <code>post-commit</code> auto-repair hook (auto-generates
orphan-<code>.md</code> siblings, idempotent + recursion-guarded); (5)
local-only final-gate ritual (remote CI DISABLED per User mandate —
operator runs <code>pre_build_verification.sh</code> + meta-test before
every tag per §11.4.40). Helper contracts:
<code>scripts/install_git_hooks.sh</code>,
<code>scripts/git_hooks/{pre-commit,pre-push,post-commit,commit-msg}</code>,
<code>_constitution_sibling_check</code>. The <code>commit-msg</code>
hook enforces a <code>Bypass-rationale: <reason></code> footer
when <code>--no-verify</code> is detected;
<code>docs/audit/bypass_events.md</code> accumulates the audit trail.
Five gates with paired §1.1 mutations:
<code>CM-COVENANT-114-75-PROPAGATION</code>,
<code>CM-GIT-HOOKS-INSTALL-SCRIPT</code>,
<code>CM-GIT-HOOKS-SOURCE-DIR</code>,
<code>CM-COMMIT-ALL-SIBLING-CHECK</code>,
<code>CM-CI-WORKFLOW-PRESENT</code>. No escape hatch — no
<code>--skip-hooks</code>, <code>--bypass-enforcement</code>,
<code>--allow-orphan-md</code>, <code>--ci-not-applicable</code>,
<code>--mechanical-enforcement-not-needed</code> flag.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.75</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-75-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. Severity-equivalent to a §11.4 PASS-bluff at the
enforcement layer. <strong>Canonical authority:</strong> constitution
submodule <code>Constitution.md</code> §11.4.75 for the full
mandate.</p>
<h2 id="11476--containers-submodule-mandate-cascaded-from-constitution-submodule-11476">§11.4.76
— Containers-Submodule Mandate (cascaded from constitution submodule
§11.4.76)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-20): <em>"For any work or requirements
of running services or codebase inside the Containers (Docker / Podman /
Qemy / Emulators, and so on) we MUST USE / INCORPORATE the Containers
Submodule properly: <a href="https://github.com/vasic-digital/containers">https://github.com/vasic-digital/containers</a>
(<a href="mailto:git@github.com">git@github.com</a>:vasic-digital/containers.git).
Containers Submodule contains all means for us to Containerize our code
and services! If any feature or Containing System is missing or not
supported we MUST EXTEND IT properly like we do all of our projects! No
bluff work is allowed of any kind!"</em></p>
</blockquote>
<p>For ANY containerized workload (Docker / Podman / Qemu / Kubernetes /
container-backed emulators), every consuming project MUST: (1) install
<code>vasic-digital/containers</code>
(<code>digital.vasic.containers</code>) as a Git submodule; (2) consume
via <code>replace</code> directive during development + pinned commit
SHAs in production; (3) boot infra on-demand via <code>pkg/boot</code> +
<code>pkg/compose</code> + <code>pkg/health</code> so operators are
never required to start <code>podman machine</code> /
<code>docker compose up</code> manually — the boot is part of the test
entry point (the on-demand-infra invariant); (4) extend the Submodule
(PR upstream) for missing runtimes / lifecycle primitives — never
reimplement in-project (per §11.4.74); (5) anti-bluff: integration tests
claiming to exercise containerized components MUST actually boot them
via the Submodule — short-circuit fakes that bypass boot are a §11.4
violation. Tracker rows touching containerization MUST record
<code>Catalogue-Check: extend vasic-digital/containers@<sha></code>
(or <code>reuse</code>). Planned gate <code>CM-CONTAINERS-USED</code>
scans container-touching PRs for
<code>digital.vasic.containers/...</code> imports; paired mutation
strips the import + asserts FAIL.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.76</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-76-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. <strong>Canonical authority:</strong> constitution
submodule <code>Constitution.md</code> §11.4.76 for the full
mandate.</p>
<h2 id="11477--regeneration-mechanism-required-mandate-cascaded-from-constitution-submodule-11477">§11.4.77
— Regeneration-Mechanism-Required Mandate (cascaded from constitution
submodule §11.4.77)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-20): <em>"We must be sure that after
excluding anything from Git versioning we still have the mechanism which
will out of the box obtain or re-generate missing content!"</em></p>
</blockquote>
<p>Every <code>.gitignore</code> entry excluding (a) >~100 MiB OR (b)
any artefact essential to building / running / testing the project MUST
carry a documented + automated mechanism to either re-obtain (download
from authoritative source: vendor tarball, SDK installer,
npm/pip/cargo/go-mod/container registry, dedicated git submodule,
S3/GCS) OR re-generate (run from tracked source via build pipeline,
code-gen, asset render, captured-evidence replay, container build).
Required artefacts per qualifying entry: (1)
<code>.gitignore-meta/<entry-slug>.yaml</code> declaring pattern +
mechanism-type + script-path + expected-disk-usage +
vendor-url-or-source + integrity hash + requires-network +
requires-credentials; (2) a non-interactive entry in
<code>scripts/setup.sh</code> post-clone bootstrap; (3) a pre-build gate
verifying regenerated content present OR a recent
<code>.gitignore-meta/.regenerated/<slug>.ok</code> stamp; (4)
README + <code>docs/guides/*.md</code> describing the mechanism + manual
fallback + time/disk budget + §11.4.10 credentials. Bare
<code>.gitignore</code> additions without the mechanism are a §11.4
PASS-bluff variant — codebase appears complete but a fresh clone cannot
build/run. No escape hatch — no <code>--skip-regen-mechanism</code>,
<code>--gitignore-is-enough</code>,
<code>--operator-already-has-content</code> flag. Planned gate
<code>CM-GITIGNORE-REGEN-MECHANISM</code> + paired §1.1 mutation (strip
a required YAML key → gate FAILs).</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.77</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-77-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. Severity-equivalent to a §11.4 PASS-bluff at the
repository-hygiene layer. <strong>Canonical authority:</strong>
constitution submodule <code>Constitution.md</code> §11.4.77 for the
full mandate.</p>
<h2 id="11478--codegraph-code-intelligence-mandate-cascaded-from-constitution-submodule-11478">§11.4.78
— CodeGraph Code-Intelligence Mandate (cascaded from constitution
submodule §11.4.78)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-20): <em>"Make codegraph MANDATORY
CHOICE for this purpose for all of our project ... All project which do
not have configured and installed codegraph yet MUST DO IT and MUST USE
IT!"</em></p>
</blockquote>
<p>Every consuming project worked on by AI coding agents MUST install,
initialize, and use <strong>CodeGraph</strong>
(<code>https://github.com/colbymchenry/codegraph</code>, npm
<code>@colbymchenry/codegraph</code>) — a local SQLite semantic
code-knowledge-graph exposed to agents over MCP (100% local, no cloud).
(1) Install globally via npm with a user-writable npm prefix (no
<code>sudo</code>). (2) <code>codegraph init</code> +
<code>codegraph index</code>: <code>.codegraph/config.json</code> is
tracked, <code>.codegraph/codegraph.db</code> is gitignored with
<code>codegraph index</code> as its §11.4.77 regeneration mechanism; the
<code>config.json</code> <code>exclude</code> list MUST exclude every
credential/secret path per §11.4.10. (3) Wire
<code>codegraph serve --mcp</code> into every CLI agent (Claude Code
<code>.mcp.json</code>, OpenCode <code>opencode.json</code>, Qwen Code
<code>.qwen/settings.json</code>, Crush <code>.crush.json</code>,
host-local otherwise) referencing the bare <code>codegraph</code>
command on <code>PATH</code> (no hardcoded host path). (4) Cover the
integration with an anti-bluff suite whose per-agent end-to-end layer
uses an unforgeable challenge (a fact obtainable only by calling a
CodeGraph MCP tool, e.g. index node count via
<code>codegraph_status</code>); a genuinely un-drivable agent is a
documented SKIP per §11.4.3, never a faked PASS. (5) Document in
<code>docs/CODEGRAPH.md</code>, kept in sync per §11.4.12 / §11.4.65.
CodeGraph is consumed as the published npm package (§11.4.74) — not a
git submodule, adds no Git remote. Planned gate
<code>CM-CODEGRAPH-WIRED</code> + paired §1.1 mutation (strip a
secret-exclusion → gate FAILs).</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.78</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-78-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. <strong>Canonical authority:</strong> constitution
submodule <code>Constitution.md</code> §11.4.78 for the full
mandate.</p>
<h2 id="11479--own-org-submodules-must-be-included-in-the-codegraph-index-cascaded-from-constitution-submodule-11479">§11.4.79
— Own-Org Submodules MUST Be Included in the CodeGraph Index (cascaded
from constitution submodule §11.4.79)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-21): <em>"All Submodules we use in the
project and that are part of organizations to which we have the full
access via GitHub, GitLab and other CLIs MUST BE included into the
codegraph database and initialized / scanned / synced!"</em></p>
</blockquote>
<p>Refines §11.4.78's exclude-list with a per-submodule-ownership split:
(a) own-org submodules (full write access via the project's CLIs —
canonical orgs <code>vasic-digital</code> +
<code>HelixDevelopment</code>) MUST be INCLUDED in the index; (b)
third-party submodules (the §11.4.74 <code>no-match → vendor</code>
path) MUST be EXCLUDED. Operational steps: (1)
<code>git submodule update --remote --merge</code> to pull latest before
re-indexing, respecting load-bearing pins on third-party submodules; (2)
adjust <code>.codegraph/config.json</code> exclude list to keep own-org
paths in scope; (3) re-index via
<code>scripts/codegraph_setup.sh</code>; (4) verify via
<code>scripts/codegraph_validate.sh</code> with ≥1 probe resolving a
symbol living ONLY inside an own-org submodule; (5) paired §1.1 mutation
— temporarily add the own-org submodule to exclude → validate MUST FAIL
on the cross-submodule probe → restore. An index that lies about
reachable symbols is a PASS-bluff against AI agents. Own-org submodules
silently excluded without an audit trail in
<code>.codegraph/config.json</code> comments is a release blocker.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.79</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-79-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. <strong>Canonical authority:</strong> constitution
submodule <code>Constitution.md</code> §11.4.79 for the full
mandate.</p>
<h2 id="11480--codegraph-regular-update--sync-automation-mandate-cascaded-from-constitution-submodule-11480">§11.4.80
— CodeGraph Regular-Update + Sync Automation Mandate (cascaded from
constitution submodule §11.4.80)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-21): <em>"We MUST regularly check for
the updates and execute codegraph npm updates so the latest version of
it is always installed on the host machine! ... Make sure we have proper
full automation bash scripts which will run regularly and that these are
part of the constitution Submodule ... Make sure all updates, sync
processes we do and important codegraph related events are all
documented under docs/codegraph in Status and Status_Summary documents
... and regularly export them like all other Status docs into the PDF
and HTML!"</em></p>
</blockquote>
<p>Three deliverables (all living in the constitution submodule,
inherited by reference per §3 — consuming projects invoke at
<code>${CONST_DIR}/scripts/codegraph_*.sh</code>, never copy): (1)
<code>scripts/codegraph_update.sh</code> — npm-installs latest
<code>@colbymchenry/codegraph</code> after a registry version check;
appends old/new version to <code>docs/codegraph/Status.md</code>;
anti-bluff verifies <code>codegraph --version</code> reflects the new
version after install (npm exit 0 ≠ working binary). (2)
<code>scripts/codegraph_sync.sh</code> — after a successful update runs
<code>codegraph status</code> → <code>codegraph sync .</code> →
<code>codegraph status</code> → the project's
<code>scripts/codegraph_validate.sh</code>; appends every step's output
to BOTH the project's and the constitution's
<code>docs/codegraph/Status.md</code>. (3)
<code>docs/codegraph/Status.md</code> + <code>Status_Summary.md</code>
append-only ledgers, exported to <code>.html</code> + <code>.pdf</code>
per §11.4.65. Cadence: weekly floor (per §11.4.45). A consuming project
that has not run <code>codegraph_update.sh</code> in >2 weeks AND has
open AI-agent work is a release blocker. Paired §1.1 mutation: downgrade
installed version → script detects drift → restore.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.80</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-80-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. <strong>Canonical authority:</strong> constitution
submodule <code>Constitution.md</code> §11.4.80 for the full
mandate.</p>
<h2 id="11481--cross-platform-parity-mandate-cascaded-from-constitution-submodule-11481">§11.4.81
— Cross-Platform-Parity Mandate (cascaded from constitution submodule
§11.4.81)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-21): <em>"Any Linux-only blocker /
issue we have MUST BE created macOS and other supported platforms
equivalent! So, depending on platform proper implementation will be used
for particular OS! EVERYTHING MUST BE PROPERLY EXTENDED AND
UPDATED!"</em></p>
</blockquote>
<p>Every consuming project whose supported-platforms manifest lists more
than one OS MUST, for every feature/test/gate/challenge/mutation
depending on platform-specific primitives, ship a per-OS-equivalent
implementation chosen at runtime via <code>uname -s</code> (or
equivalent detection). Three sub-mandates: <strong>(A) Per-OS
implementation REQUIRED</strong> — Linux
cgroup/systemd/<code>/proc</code> primitives MUST have documented per-OS
equivalents (POSIX <code>setrlimit</code>/<code>ulimit</code>, macOS
<code>launchd</code>, BSD <code>rctl</code>, Windows Job Object) chosen
via runtime dispatch. <strong>(B) Per-OS tests REQUIRED</strong> — every
platform-dependent gate test MUST have
<code>case "$(uname -s)" in</code> branches with positive captured
evidence per §11.4.2 + §11.4.5 in each branch; SKIP-with-reason
acceptable ONLY when the platform genuinely cannot enforce the
invariant. <strong>(C) Honest kernel-gap citation + adjacent equivalent
test REQUIRED</strong> — where a Linux primitive has NO equivalent due
to a documented kernel limitation (canonical: XNU does not enforce
<code>RLIMIT_AS</code> for unprivileged processes), the test MUST detect
the gap at runtime, SKIP with exact kernel reason + reproducer +
honest-gap-doc link, AND provide an ADJACENT test exercising the closest
invariant the platform CAN enforce (e.g.
<code>RLIMIT_CPU</code>+<code>SIGXCPU</code> as the macOS proxy), itself
anti-bluff with a paired §1.1 mutation. Gate
<code>CM-CROSS-PLATFORM-PARITY</code> scans for
<code>case "$(uname -s)"</code> blocks asserting a non-SKIP branch (or
honest-gap citation) per platform in the manifest; paired mutation
strips a Darwin branch → gate FAILs. No escape hatch.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.81</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-81-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. Release blocker on multi-platform projects.
<strong>Canonical authority:</strong> constitution submodule
<code>Constitution.md</code> §11.4.81 for the full mandate.</p>
<h2 id="11482--iteration-speedup-discipline-mandate-cascaded-from-constitution-submodule-11482">§11.4.82
— Iteration-Speedup Discipline Mandate (cascaded from constitution
submodule §11.4.82)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-22): <em>"How can we speed-up this
whole development and fixing process? ... Do not forget to all speed
optimizations critical rules and mandatory constraints MUST BE all added
into our root (constitution Submodule) Constitution.md, CLAUDE.md,
AGENTS.md and QWEN.md and all other relevant constitution Submodules
files!"</em></p>
</blockquote>
<p>Iteration cycle time is a first-order quality enabler. Every
consuming project's build / test / commit / debug pipeline MUST adopt
these speedup disciplines AS MANDATORY (each independently enforceable):
(A) Phase-1 forensic (<code>superpowers:systematic-debugging</code>)
before any speculative source patch — speculative patches without
FACT-grade root cause are §11.4.6 + §11.4.82 violations; (B)
Live-ADB-First (or live-equivalent) before any rebuild — strengthens
§11.4.51 to a release-blocker mandate; (C) 30-second pre-flight before
launching rebuild orchestrators (device/sink reachability, host
memory/disk, no stale locks, no orphan processes); (D) persistent build
caches outside containers
(<code>ccache</code>/<code>sccache</code>/Gradle daemon bind-mounted to
host); (E) module-only rebuild for loadable-module-only changes; (F)
parallel multi-device testing with separate
<code>qa-results/<TS>/<device-tag>/</code> outputs; (G)
subagent scope discipline + worktree isolation (≤30 min budget,
single-responsibility, <code>isolation: "worktree"</code> default); (H)
lock-file + stale-process hygiene (clean <code>.git/index.lock</code>,
disable auto git-gc in concurrent repos); (I) cycle telemetry per
§11.4.24 (commit hash, per-phase wall-clock, speedup-flag set, outcome —
aggregated weekly). Gate <code>CM-ITERATION-SPEEDUP-DISCIPLINE</code>
audits recent cycles for telemetry citing which of (A)-(I) applied;
paired §1.1 mutation strips the speedup-flag column → gate FAILs. No
escape hatch — no <code>--skip-phase1-forensic</code>,
<code>--no-pre-flight</code>, <code>--rebuild-everything-always</code>,
<code>--unlimited-subagent-scope</code>, <code>--ignore-locks</code>,
<code>--no-telemetry</code> flag.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.82</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-82-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. Release blocker. <strong>Canonical
authority:</strong> constitution submodule <code>Constitution.md</code>
§11.4.82 for the full mandate.</p>
<h2 id="11483--docsqa-end-user-evidence-mandate-cascaded-from-constitution-submodule-11483">§11.4.83
— docs/qa/ End-User Evidence Mandate (cascaded from constitution
submodule §11.4.83)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-22): <em>"every feature that ships
MUST carry a recorded e2e communication transcript + any attached
materials under <code>docs/qa/<run-id>/</code> (per-feature
subdirectories). A feature with no QA transcript is itself a §107
PASS-bluff — it claims to work but has no auditable runtime evidence.
Bot-driven automation MUST preserve full bidirectional communication
threads as proof."</em></p>
</blockquote>
<p>Every feature that ships MUST carry a recorded end-to-end
communication transcript plus any attached materials (screenshots,
request/response payloads, audio, file uploads) committed under
<code>docs/qa/<run-id>/</code> — one directory per feature run.
Operative rule: (1) every consuming project MUST maintain a
<code>docs/qa/</code> tree, each new feature under
<code>docs/qa/<run-id>/</code> where <code><run-id></code>
is monotonic + greppable (timestamp / ATM-NNN / other workable-item ID
per §11.4.54); (2) transcripts MUST be full bidirectional — every
prompt/command sent + every response received (one-sided is not a
transcript); (3) attached materials MUST be committed in-repo (no
external-only links — that is a §11.4.13 sink-side violation); (4)
bot-driven / agent-driven QA automation MUST preserve the full
conversation thread as the proof artefact; (5) release gates MUST refuse
to tag a version that has any feature-shipping commit without its
matching <code>docs/qa/<run-id>/</code> directory. A feature with
no QA transcript is a §11.4 / §107 PASS-bluff. Composes with §11.4.2 /
§11.4.5 / §11.4.13 / §11.4.65 / §11.4.69 / §1.1.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.83</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-83-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. Release blocker — no
<code>--qa-evidence-optional</code> escape hatch. <strong>Canonical
authority:</strong> constitution submodule <code>Constitution.md</code>
§11.4.83 for the full mandate.</p>
<h2 id="11484--working-tree-quiescence-rule-for-subagent-commits-cascaded-from-constitution-submodule-11484">§11.4.84
— Working-Tree Quiescence Rule for Subagent Commits (cascaded from
constitution submodule §11.4.84)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-22): <em>"no subagent commit may
proceed while any concurrent mutation gate is in flight in the same
checkout. Before <code>git add</code>, the committing agent MUST
<code>grep</code> its own working tree for mutation markers
(<code>MUTATED for paired</code>, <code>// always pass</code>,
<code>return json.Marshal</code> shortcut paths, etc.). Any unexplained
file in the staging area triggers ABORT."</em></p>
</blockquote>
<p>No subagent (or main-thread) commit may proceed while any concurrent
mutation gate, paired-mutation experiment, or other in-flight mutation
is live in the same checkout. Before <code>git add</code>, the
committing agent MUST grep its own working tree for mutation markers
(<code>MUTATED for paired</code>, <code>// always pass</code>,
<code>return json.Marshal</code> shortcut paths,
<code>// MUTATION</code> / <code># MUTATION</code> annotations,
<code>_mutated_*</code> filename suffixes, etc.) and explicitly account
for every modified file in the staging area; any unexplained file →
ABORT. (Forensic case: a logo-fix subagent's <code>git add</code> swept
an <code>// always pass</code> JWT-verify mutation residue into an
unrelated commit pushed to all four mirrors — a real security-defect
window.) Operative rule: (1) pre-<code>git add</code> greps for mutation
markers + cross-checks <code>git status --porcelain</code> against the
subagent's declared scope; unaccounted entries → ABORT; (2) any active
mutation gate MUST be serialised (mutate → assert FAIL → restore →
assert PASS) and the working tree verifiably clean before any unrelated
commit; (3) concurrent subagents in the SAME checkout MUST coordinate
through a lockfile (<code>.git/MUTATION_IN_PROGRESS</code>) — cleaner
solution is <code>git worktree add</code> per subagent (composes with
§11.4.20/§11.4.70); (4) post-commit
<code>mutation-residue-scanner</code> MUST run before push — any commit
containing a mutation marker → push BLOCKED.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.84</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-84-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. A mutation marker that lands in a tagged commit is
a critical defect regardless of how briefly it persisted.
<strong>Canonical authority:</strong> constitution submodule
<code>Constitution.md</code> §11.4.84 for the full mandate.</p>
<h2 id="11485--stress--chaos-test-mandate-cascaded-from-constitution-submodule-11485">§11.4.85
— Stress + Chaos Test Mandate (cascaded from constitution submodule
§11.4.85)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-24): <em>"Every fix or improvement you
do MUST BE covered with full automation stress and chaos tests so we are
sure nothing can break the functionality and all edge cases are
monitored and polished and additionally fixed if that is needed!
Everything must produce rock solid proofs and follow fully no-bluff
policy!"</em></p>
</blockquote>
<p>Every fix or improvement landed MUST ship with full-automation
<strong>stress</strong> AND <strong>chaos</strong> test suites
exercising edge cases, sustained load, concurrent contention, and
failure-injection. Happy-path coverage alone is a §11.4 / §107
PASS-bluff at the resilience layer. <strong>Stress</strong>
(closed-set): sustained load (N ≥ 100 iterations OR ≥ 30 s wall-clock,
p50/p95/p99 latency recorded) + concurrent contention (N ≥ 10 parallel
invocations, no deadlock/leak) + boundary conditions
(empty/max/off-by-one, each categorised). <strong>Chaos</strong>
(closed-set, per fix-class appropriateness): process-death injection +
network-fault injection (drop/delay/reorder) + input-corruption
injection + resource-exhaustion injection (disk full, OOM, FD exhaustion
— refuse cleanly OR degrade, NEVER crash) + state-corruption injection
(mid-flight lock loss, partial-write). Every stress + chaos PASS MUST
cite a captured-evidence artefact path per §11.4.5 + §11.4.69. Helper
library <code>stress_chaos.sh</code> provides
<code>ab_stress_run</code>, <code>ab_stress_concurrent</code>,
<code>ab_chaos_kill_pid_during</code>,
<code>ab_chaos_drop_network_during</code>,
<code>ab_chaos_corrupt_file_during</code>,
<code>ab_chaos_oom_pressure_during</code>,
<code>ab_chaos_disk_full_during</code>, each composing with
<code>ab_pass_with_evidence</code> / <code>ab_skip_with_reason</code>.
Cleanup non-negotiable in <code>trap '...' EXIT</code> (cleanup failure
= §11.4.14 violation). Four-layer coverage per §11.4.4(b) + paired §1.1
mutation (strip chaos-injection or evidence-capture → gate FAILs). No
escape hatch — no <code>--skip-stress</code>, <code>--no-chaos</code>,
<code>--happy-path-suffices</code>, <code>--stress-test-later</code>
flag.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.85</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-85-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. Release blocker. <strong>Canonical
authority:</strong> constitution submodule <code>Constitution.md</code>
§11.4.85 for the full mandate.</p>
<h2 id="11486--rostercorpus-backed-status-doc-auto-sync-mandate-cascaded-from-constitution-submodule-11486">§11.4.86
— Roster/Corpus-Backed Status-Doc Auto-Sync Mandate (cascaded from
constitution submodule §11.4.86)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-25): <em>"Make sure that assets and
players Status docs are ALWAYS regularly updated and in sync like all
others Status docs — any time we add or modify the assets content(s) or
we change or add new / remove existing pre-installed video and audio
player apps! This MUST WORK OUT OF THE BOX!"</em></p>
</blockquote>
<p>Some Status docs (§11.4.45) are backed by a tracked roster (installed
apps/components) or a tracked asset corpus (test/media asset directory)
rather than narrative alone. Their freshness MUST NOT depend on operator
vigilance — the moment a roster/corpus member changes (app
added/removed/renamed; asset added/modified/removed) the Status doc +
Status_Summary + HTML + PDF MUST resync out of the box, mechanically.
Mechanism (all must hold): (1) drift-proof fingerprint — sha256 of the
sorted member list (NOT mtime), persisted in a sidecar beside the Status
doc; (2) a sync helper that regenerates the fingerprint + re-exports
HTML+PDF via the §11.4.65 exporter, wired so sync is automatic; (3) a
pre-build gate that FAILs when the live fingerprint differs from the
persisted one (mirrors §11.4.12 <code>CM-ISSUES-SUMMARY-SYNC</code> +
§11.4.45 <code>sync_integration_status</code>); (4) a paired §1.1
mutation corrupting the fingerprint and asserting the gate FAILs.
Classification: universal — the consuming project supplies the specific
docs, roster/corpus sources, helper, and gate name per §11.4.35.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>§11.4.86</code> reference) MUST appear in every owned submodule's
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Propagation gate
<code>CM-COVENANT-114-86-PROPAGATION</code>; paired mutation strips the
literal → gate FAILs. Release blocker — no