-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathCONSTITUTION.html
More file actions
4911 lines (4905 loc) · 274 KB
/
Copy pathCONSTITUTION.html
File metadata and controls
4911 lines (4905 loc) · 274 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">
<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>CONSTITUTION</title>
<style>
/* Default styles provided by pandoc.
** See https://pandoc.org/MANUAL.html#variables-for-html for config info.
*/
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 {
white-space: pre-wrap;
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;
}
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;}
/* The extra [class] is a hack that increases specificity enough to
override a similar rule in reveal.js */
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;}
/* CSS for syntax highlighting */
html { -webkit-text-size-adjust: 100%; }
pre > code.sourceCode { white-space: pre; position: relative; }
pre > code.sourceCode > span { display: inline-block; line-height: 1.25; }
pre > code.sourceCode > span:empty { height: 1.2em; }
.sourceCode { overflow: visible; }
code.sourceCode > span { color: inherit; text-decoration: inherit; }
div.sourceCode { margin: 1em 0; }
pre.sourceCode { margin: 0; }
@media screen {
div.sourceCode { overflow: auto; }
}
@media print {
pre > code.sourceCode { white-space: pre-wrap; }
pre > code.sourceCode > span { text-indent: -5em; padding-left: 5em; }
}
pre.numberSource code
{ counter-reset: source-line 0; }
pre.numberSource code > span
{ position: relative; left: -4em; counter-increment: source-line; }
pre.numberSource code > span > a:first-child::before
{ content: counter(source-line);
position: relative; left: -1em; text-align: right; vertical-align: baseline;
border: none; display: inline-block;
-webkit-touch-callout: none; -webkit-user-select: none;
-khtml-user-select: none; -moz-user-select: none;
-ms-user-select: none; user-select: none;
padding: 0 4px; width: 4em;
color: #aaaaaa;
}
pre.numberSource { margin-left: 3em; border-left: 1px solid #aaaaaa; padding-left: 4px; }
div.sourceCode
{ }
@media screen {
pre > code.sourceCode > span > a:first-child::before { text-decoration: underline; }
}
code span.al { color: #ff0000; font-weight: bold; } /* Alert */
code span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */
code span.at { color: #7d9029; } /* Attribute */
code span.bn { color: #40a070; } /* BaseN */
code span.bu { color: #008000; } /* BuiltIn */
code span.cf { color: #007020; font-weight: bold; } /* ControlFlow */
code span.ch { color: #4070a0; } /* Char */
code span.cn { color: #880000; } /* Constant */
code span.co { color: #60a0b0; font-style: italic; } /* Comment */
code span.cv { color: #60a0b0; font-weight: bold; font-style: italic; } /* CommentVar */
code span.do { color: #ba2121; font-style: italic; } /* Documentation */
code span.dt { color: #902000; } /* DataType */
code span.dv { color: #40a070; } /* DecVal */
code span.er { color: #ff0000; font-weight: bold; } /* Error */
code span.ex { } /* Extension */
code span.fl { color: #40a070; } /* Float */
code span.fu { color: #06287e; } /* Function */
code span.im { color: #008000; font-weight: bold; } /* Import */
code span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */
code span.kw { color: #007020; font-weight: bold; } /* Keyword */
code span.op { color: #666666; } /* Operator */
code span.ot { color: #007020; } /* Other */
code span.pp { color: #bc7a00; } /* Preprocessor */
code span.sc { color: #4070a0; } /* SpecialChar */
code span.ss { color: #bb6688; } /* SpecialString */
code span.st { color: #4070a0; } /* String */
code span.va { color: #19177c; } /* Variable */
code span.vs { color: #4070a0; } /* VerbatimString */
code span.wa { color: #60a0b0; font-weight: bold; font-style: italic; } /* Warning */
</style>
</head>
<body>
<header id="title-block-header">
<h1 class="title">CONSTITUTION</h1>
</header>
<h2 id="inherited-from-helix-constitution">INHERITED FROM Helix
Constitution</h2>
<p>This module is a submodule of a Helix-family project (e.g. HelixCode,
HelixAgent, ATMOSphere) that includes the Helix Constitution submodule
at the parent's <code>constitution/</code> path. All rules in
<code>constitution/CLAUDE.md</code> and the
<code>constitution/Constitution.md</code> it references (universal
anti-bluff covenant §11.4, no-guessing mandate §11.4.6,
credentials-handling mandate §11.4.10, host-session safety §12, data
safety §9, mutation- paired gates §1.1) apply unconditionally to every
change landed here. The module-specific rules below extend them — they
never weaken any universal clause.</p>
<p>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>Canonical reference: <a
href="https://github.com/HelixDevelopment/HelixConstitution">https://github.com/HelixDevelopment/HelixConstitution</a></p>
<hr />
<h1 id="helixcode-constitution">HelixCode Constitution</h1>
<blockquote>
<p><strong>Inherits from:</strong>
<code>HelixConstitution/Constitution.md</code> — all universal clauses
in that document apply unconditionally. Rules below extend or tighten
them; they MUST NOT weaken any inherited clause.</p>
</blockquote>
<h2 id="helixcode-project-constitution">HelixCode Project
Constitution</h2>
<p><strong>Version</strong>: 1.0.0 <strong>Effective Date</strong>:
2026-04-30 <strong>Scope</strong>: This Constitution applies to
HelixCode and ALL its submodules <strong>Authority</strong>: Cascaded
from HelixAgent root governance with HelixCode-specific addenda</p>
<hr />
<h2 id="preamble">Preamble</h2>
<p>HelixCode is an enterprise-grade distributed AI development platform.
This Constitution establishes the non-negotiable rules that govern all
development, testing, deployment, and maintenance activities within the
project. Every contributor, agent, and automated process MUST adhere to
these rules. No exceptions.</p>
<hr />
<h2 id="const-001-no-cicd-pipelines-permanent">CONST-001: No CI/CD
Pipelines (Permanent)</h2>
<p>No <code>.github/workflows/</code>, <code>.gitlab-ci.yml</code>,
<code>Jenkinsfile</code>, <code>.travis.yml</code>,
<code>.circleci/</code>, or any automated pipeline. No Git hooks. All
builds and tests run manually or via Makefile/script targets.</p>
<p><strong>Rationale</strong>: Manual execution ensures human oversight
and prevents automated propagation of bluffs.</p>
<hr />
<h2 id="const-002-no-mocks-in-production-permanent">CONST-002: No Mocks
in Production (Permanent)</h2>
<h3 id="const-002a-production-code">CONST-002a: Production Code</h3>
<p>Mocks, stubs, fakes, placeholder classes, TODO implementations are
STRICTLY FORBIDDEN in production code. All production code is fully
functional with real integrations.</p>
<h3 id="const-002b-test-code">CONST-002b: Test Code</h3>
<p>Mocks/stubs/fakes MAY be used ONLY in unit tests (files ending
<code>_test.go</code> run under <code>go test -short</code>).</p>
<p><strong>Rationale</strong>: Production bluffs have repeatedly been
discovered where features appeared implemented but were
non-functional.</p>
<hr />
<h2 id="const-003-no-https-for-git-permanent">CONST-003: No HTTPS for
Git (Permanent)</h2>
<p>SSH URLs only (<code>git@github.com:…</code>,
<code>git@gitlab.com:…</code>, etc.) for clones, fetches, pushes, and
submodule updates. SSH keys are configured on every service.</p>
<hr />
<h2 id="const-004-no-manual-container-commands-permanent">CONST-004: No
Manual Container Commands (Permanent)</h2>
<p>Container orchestration is owned by the project's binary/orchestrator
(e.g., <code>make build</code> → <code>./bin/<app></code>). Direct
<code>docker</code>/<code>podman start|stop|rm</code> and
<code>docker-compose up|down</code> are prohibited as workflows.</p>
<hr />
<h2 id="const-005-100-real-data-for-non-unit-tests">CONST-005: 100% Real
Data for Non-Unit Tests</h2>
<p>Beyond unit tests, all components MUST use actual API calls, real
databases, live services. No simulated success. Fallback chains tested
with actual failures.</p>
<p><strong>Verification</strong>: Every integration/E2E test MUST
connect to real services or skip (not fail) if unavailable.</p>
<hr />
<h2 id="const-006-challenge-coverage-permanent">CONST-006: Challenge
Coverage (Permanent)</h2>
<p>Every component MUST have Challenge scripts
(<code>./challenges/scripts/</code>) validating real-life use cases. No
false success — validate actual behavior, not return codes.</p>
<hr />
<h2 id="const-007-health--observability">CONST-007: Health &
Observability</h2>
<p>Every service MUST expose health endpoints. Circuit breakers for all
external dependencies. Prometheus / OpenTelemetry integration where
applicable.</p>
<hr />
<h2 id="const-008-documentation--quality">CONST-008: Documentation &
Quality</h2>
<p>Update <code>CLAUDE.md</code>, <code>AGENTS.md</code>, and relevant
docs alongside code changes. Pass language-appropriate
format/lint/security gates. Conventional Commits:
<code><type>(<scope>): <description></code>.</p>
<hr />
<h2 id="const-009-validation-before-release">CONST-009: Validation
Before Release</h2>
<p>Pass the project's full validation suite
(<code>make ci-validate-all</code>-equivalent) plus all challenges
(<code>./challenges/scripts/run_all_challenges.sh</code>).</p>
<hr />
<h2 id="const-010-comprehensive-verification">CONST-010: Comprehensive
Verification</h2>
<p>Every fix MUST be verified from all angles: runtime testing (actual
HTTP requests / real CLI invocations), compile verification, code
structure checks, dependency existence checks, backward compatibility,
and no false positives. Grep-only validation is NEVER sufficient.</p>
<hr />
<h2 id="const-011-resource-limits-for-tests--challenges">CONST-011:
Resource Limits for Tests & Challenges</h2>
<p>ALL test and challenge execution MUST be strictly limited to 30-40%
of host system resources. Use <code>GOMAXPROCS=2</code>,
<code>nice -n 19</code>, <code>ionice -c 3</code>, <code>-p 1</code> for
<code>go test</code>. Container limits required.</p>
<hr />
<h2 id="const-012-bugfix-documentation">CONST-012: Bugfix
Documentation</h2>
<p>All bug fixes MUST be documented in
<code>docs/issues/fixed/BUGFIXES.md</code> with root cause analysis,
affected files, fix description, and a link to the verification
test/challenge.</p>
<hr />
<h2 id="const-013-real-infrastructure-for-all-non-unit-tests">CONST-013:
Real Infrastructure for All Non-Unit Tests</h2>
<p>Mocks/fakes/stubs/placeholders MAY be used ONLY in unit tests. ALL
other test types — integration, E2E, functional, security, stress,
chaos, challenge, benchmark, runtime verification — MUST execute against
REAL running systems with REAL containers, REAL databases, REAL
services, and REAL HTTP calls.</p>
<hr />
<h2 id="const-014-reproduction-before-fix-mandatory">CONST-014:
Reproduction-Before-Fix (Mandatory)</h2>
<p>Every reported error, defect, or unexpected behavior MUST be
reproduced by a Challenge script BEFORE any fix is attempted.
Sequence:</p>
<ol type="1">
<li>Write the Challenge first</li>
<li>Run it; confirm fail (it reproduces the bug)</li>
<li>Then write the fix</li>
<li>Re-run; confirm pass</li>
<li>Commit Challenge + fix together</li>
</ol>
<p>The Challenge becomes the regression guard for that bug forever.</p>
<hr />
<h2 id="const-015-concurrent-safe-containers">CONST-015: Concurrent-Safe
Containers</h2>
<p>Any struct field that is a mutable collection (map, slice) accessed
concurrently MUST use thread-safe primitives. Bare
<code>sync.Mutex + map/slice</code> combinations are prohibited for new
code.</p>
<hr />
<h2 id="const-016-definition-of-done-universal">CONST-016: Definition of
Done (Universal)</h2>
<p>A change is NOT done because code compiles and tests pass. "Done"
requires pasted terminal output from a real run.</p>
<ul>
<li><strong>No self-certification</strong>: Words like <em>verified,
tested, working, complete, fixed, passing</em> are forbidden in
commits/PRs/replies unless accompanied by pasted output from a command
that ran in that session.</li>
<li><strong>Demo before code</strong>: Every task begins by writing the
runnable acceptance demo</li>
<li><strong>Real system, every time</strong>: Demos run against real
artifacts</li>
<li><strong>Skips are loud</strong>: <code>t.Skip</code> without a
trailing <code>SKIP-OK: #<ticket></code> comment breaks
validation</li>
</ul>
<hr />
<h2
id="const-035--anti-bluff-tests--challenges-user-mandate-forensic-anchor">CONST-035
— Anti-Bluff Tests & Challenges (User-Mandate Forensic Anchor)</h2>
<p><strong>§11.9 User-Mandate Forensic Anchor (2026-04-29)</strong></p>
<p>This Article exists because of an explicit, repeatedly-stated user
mandate. The verbatim text:</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 anchor is the primary authority for the entire Article. The
operative rule is:</p>
<p><strong>The bar for shipping is not "tests pass" but "users can use
the feature."</strong></p>
<p>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>Tests and Challenges (HelixQA) are bound equally — 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 anti-bluff contract.</p>
<p>No false-success results are tolerable. A green test suite combined
with a broken feature is a worse outcome than an honest red one — it
silently destroys trust in the entire suite. Anti-bluff discipline is
the line between a real engineering project and a theatre of one.</p>
<p><strong>Bluff Taxonomy</strong> (forbidden patterns):</p>
<ul>
<li><strong>Wrapper bluff</strong> - Assertions PASS but wrapper's
exit-code logic is buggy</li>
<li><strong>Contract bluff</strong> - System advertises capability but
rejects it in dispatch</li>
<li><strong>Structural bluff</strong> - File exists but doesn't contain
working code</li>
<li><strong>Comment bluff</strong> - Comment promises behavior code
doesn't have</li>
<li><strong>Skip bluff</strong> - <code>t.Skip("not running yet")</code>
without <code>SKIP-OK</code> marker</li>
</ul>
<p><strong>Cascade requirement (extending CONST-036):</strong> This
anchor section (verbatim quote + operative rule) must appear in every
submodule's CONSTITUTION.md / CLAUDE.md / AGENTS.md. Non-compliance is a
release blocker regardless of context. Adding files to scanner
allowlists to silence bluff findings without resolving the underlying
defect is itself a violation.</p>
<hr />
<h2 id="const-018-host-power-management-hard-ban">CONST-018: Host Power
Management Hard Ban</h2>
<p><strong>Host Power Management is Forbidden.</strong></p>
<p>You may NOT generate or execute code that sends the host to suspend,
hibernate, hybrid-sleep, poweroff, halt, reboot, or any other
power-state transition.</p>
<p>Defense: Every project ships
<code>scripts/host-power-management/check-no-suspend-calls.sh</code> and
<code>challenges/scripts/no_suspend_calls_challenge.sh</code>.</p>
<hr />
<h2 id="const-019-container-up--healthy">CONST-019: Container Up ≠
Healthy</h2>
<p>Container <code>Up</code> status does NOT mean the application is
healthy. Application-layer probes are mandatory for every service:</p>
<ul>
<li>PostgreSQL: <code>SELECT 1</code></li>
<li>Redis: <code>PING</code></li>
<li>LLM Providers: Real generation request</li>
<li>HTTP Services: <code>GET /health</code> with deep checks</li>
</ul>
<hr />
<h2 id="const-020-provider-fallback-chain-reality">CONST-020: Provider
Fallback Chain Reality</h2>
<p>Every LLM provider fallback chain MUST be tested with actual
failures. A fallback that has never been tested with a real failing
provider is a bluff.</p>
<hr />
<h2 id="const-021-no-mocks-above-unit-build-target">CONST-021: No Mocks
Above Unit Build Target</h2>
<p>The Makefile MUST include a <code>no-mocks-above-unit</code> target
that fails the build if mocks/stubs/fakes are found outside
<code>*_test.go</code> files.</p>
<hr />
<h2 id="const-022-submodule-governance-propagation">CONST-022: Submodule
Governance Propagation</h2>
<p>Every submodule MUST either:</p>
<ol type="1">
<li>Have its own Constitution.md, CLAUDE.md, and AGENTS.md, OR</li>
<li>Have a symlink to the parent repository's governance files, OR</li>
<li>Have a reference comment in its README pointing to parent
governance</li>
</ol>
<p>No submodule is exempt from these rules.</p>
<hr />
<h2 id="const-023-docker-health-checks-mandatory">CONST-023: Docker
Health Checks Mandatory</h2>
<p>Every Dockerfile MUST include:</p>
<div class="sourceCode" id="cb1"><pre
class="sourceCode dockerfile"><code class="sourceCode dockerfile"><span id="cb1-1"><a href="#cb1-1" aria-hidden="true" tabindex="-1"></a><span class="kw">HEALTHCHECK</span> <span class="op">--interval=30s</span> <span class="op">--timeout=10s</span> <span class="op">--start-period=5s</span> <span class="op">--retries=3</span> \</span>
<span id="cb1-2"><a href="#cb1-2" aria-hidden="true" tabindex="-1"></a> <span class="kw">CMD</span> <span class="ex">curl</span> <span class="at">-f</span> http://localhost:8080/health <span class="kw">||</span> <span class="bu">exit</span> 1</span></code></pre></div>
<p>The health endpoint MUST perform deep checks (database connection,
provider availability), not just return HTTP 200.</p>
<hr />
<h2 id="const-024-version-pinning">CONST-024: Version Pinning</h2>
<p>All dependencies MUST be pinned to specific versions in
<code>go.mod</code>. No <code>latest</code>, no floating tags. Renovate
or Dependabot (manual review only — see CONST-001) may propose
updates.</p>
<hr />
<h2 id="const-025-secret-management">CONST-025: Secret Management</h2>
<p>NO secrets in code. EVER. Secrets via:</p>
<ul>
<li>Environment variables (production)</li>
<li><code>.env</code> files (development, in
<code>.gitignore</code>)</li>
<li>Vault/Secret Manager (enterprise)</li>
<li>Docker secrets (containerized)</li>
</ul>
<p><code>go mod tidy</code> MUST NOT add secret-scanning bypasses.</p>
<hr />
<h2 id="const-026-minimal-privilege-containers">CONST-026: Minimal
Privilege Containers</h2>
<p>Containers run as non-root. Every Dockerfile:</p>
<div class="sourceCode" id="cb2"><pre
class="sourceCode dockerfile"><code class="sourceCode dockerfile"><span id="cb2-1"><a href="#cb2-1" aria-hidden="true" tabindex="-1"></a><span class="kw">RUN</span> <span class="ex">adduser</span> <span class="at">-D</span> <span class="at">-u</span> 1001 helixcode</span>
<span id="cb2-2"><a href="#cb2-2" aria-hidden="true" tabindex="-1"></a><span class="kw">USER</span> helixcode</span></code></pre></div>
<hr />
<h2 id="const-027-network-isolation">CONST-027: Network Isolation</h2>
<p>Container orchestration MUST use internal networks. Services
communicate via named hosts, not exposed ports where possible.</p>
<hr />
<h2 id="const-028-backup-before-destructive-operations">CONST-028:
Backup Before Destructive Operations</h2>
<p>Every file editing tool MUST create backups before modification. The
backup MUST be restorable.</p>
<hr />
<h2 id="const-029-input-validation-at-all-boundaries">CONST-029: Input
Validation at All Boundaries</h2>
<p>Every public function MUST validate inputs. No trust of
caller-provided data. SQL injection, path traversal, command injection
MUST be impossible by design.</p>
<hr />
<h2 id="const-030-graceful-degradation">CONST-030: Graceful
Degradation</h2>
<p>When external services are unavailable, the system MUST degrade
gracefully:</p>
<ul>
<li>Return partial results where possible</li>
<li>Queue operations for retry</li>
<li>Inform user of degraded state</li>
<li>NEVER crash or hang indefinitely</li>
</ul>
<hr />
<h2 id="const-031-audit-trail">CONST-031: Audit Trail</h2>
<p>Every significant operation MUST be logged with:</p>
<ul>
<li>Timestamp</li>
<li>User identity</li>
<li>Operation type</li>
<li>Success/failure status</li>
<li>Resource affected</li>
</ul>
<p>Log retention: 90 days minimum.</p>
<hr />
<h2 id="const-032-emergency-stop">CONST-032: Emergency Stop</h2>
<p>Every long-running or distributed operation MUST support cancellation
via <code>context.Context</code>. Users MUST be able to interrupt any
operation.</p>
<hr />
<h2 id="const-033-data-integrity">CONST-033: Data Integrity</h2>
<p>Database writes MUST be transactional. Partial writes MUST be rolled
back. Consistency checks MUST run periodically.</p>
<hr />
<h2 id="const-034-api-stability">CONST-034: API Stability</h2>
<p>Public APIs maintain backward compatibility within major versions.
Deprecation requires:</p>
<ul>
<li>6-month notice</li>
<li>Migration guide</li>
<li>Compatibility shim</li>
</ul>
<hr />
<h2
id="const-035-end-user-usability-mandate-2026-04-29-strengthening">CONST-035:
End-User Usability Mandate (2026-04-29 Strengthening)</h2>
<p>A test or Challenge that PASSES is a CLAIM that the tested behavior
<strong>works for the end user of the product</strong>.</p>
<p>The HelixAgent project has repeatedly hit the failure mode where
every test ran green AND every Challenge reported PASS, yet most product
features did not actually work. This MUST NOT recur in HelixCode.</p>
<p>Every PASS result MUST guarantee: a. <strong>Quality</strong> -
correct behavior under real inputs, edge cases, concurrency b.
<strong>Completion</strong> - wired end-to-end with no stub/placeholder
gaps c. <strong>Full usability</strong> - a user following documented
request shapes SUCCEEDS</p>
<p>A passing test that doesn't certify all three is a
<strong>bluff</strong> and MUST be tightened.</p>
<p><strong>Bluff taxonomy</strong> (each pattern observed and now
forbidden):</p>
<ul>
<li><strong>Wrapper bluff</strong> - assertions PASS but wrapper's
exit-code logic is buggy</li>
<li><strong>Contract bluff</strong> - system advertises capability but
rejects it in dispatch</li>
<li><strong>Structural bluff</strong> - <code>check_file_exists</code>
passes but doesn't run the test</li>
<li><strong>Comment bluff</strong> - comment promises behavior code
doesn't actually have</li>
<li><strong>Skip bluff</strong> - <code>t.Skip("not running yet")</code>
without <code>SKIP-OK: #<ticket></code> marker</li>
</ul>
<p><strong>Full background</strong>:
<code>docs/HOST_POWER_MANAGEMENT.md</code> and this Constitution
(CONST-035).</p>
<hr />
<h2 id="const-036-propagation-to-submodules">CONST-036: Propagation to
Submodules</h2>
<p>This Constitution, along with CLAUDE.md and AGENTS.md, MUST be
propagated to ALL submodules. Each submodule's governance MUST reference
this parent Constitution. Changes to this Constitution MUST trigger
review of all submodule governance files.</p>
<hr />
<h2
id="const-037-llmsverifier-single-source-of-truth-mandate">CONST-037:
LLMsVerifier Single Source of Truth Mandate</h2>
<p><strong>Rule</strong>: LLMsVerifier SHALL BE the sole authoritative
source for:</p>
<ol type="1">
<li>All model metadata (names, IDs, context windows, capabilities)</li>
<li>All provider metadata (endpoints, auth types, supported models)</li>
<li>All verification status (verified, partial, failed, pending)</li>
<li>All scoring data (overall scores, capability scores, tier
rankings)</li>
<li>All rate-limit and cooldown state</li>
</ol>
<p><strong>Prohibition</strong>: NO hardcoded model lists, NO hardcoded
provider lists, NO simulated model discovery. Any code path that
presents a model or provider listing to a user MUST fetch that listing
from the LLMsVerifier subsystem or its cached replica.</p>
<p><strong>Anti-Bluff Verification</strong>:</p>
<ul>
<li>The challenge script
<code>challenges/scripts/verifier_hardcode_check.sh</code> MUST scan all
Go source files for hardcoded model arrays.</li>
<li>Any <code>[]string{"gpt-4", "claude-3"}</code> or equivalent literal
in production code is a constitutional violation.</li>
<li>The only permitted hardcoded data is the LLMsVerifier service
endpoint URL and the list of verification test types.</li>
</ul>
<p><strong>Enforcement</strong>: <code>make test-complete</code> MUST
include a test that asserts
<code>ModelManager.GetAvailableModels()</code> returns at least as many
models as the verifier's database contains for configured providers. A
test that passes while the CLI shows a hardcoded list is a TEST BLUFF
and violates CONST-035.</p>
<hr />
<h2 id="const-038-model-provider-anti-bluff-guarantee">CONST-038: Model
Provider Anti-Bluff Guarantee</h2>
<p><strong>Rule</strong>: Every model displayed to an end user MUST have
been verified by LLMsVerifier within the last
<code>verification_timeout</code> period (default: 24h). Models older
than this MUST display a "stale" indicator and be deprioritized.</p>
<p><strong>Prohibition Against Test Bluffing</strong>:</p>
<ul>
<li>A unit test that mocks the verifier client and asserts
<code>GetAvailableModels()</code> returns 3 models DOES NOT satisfy this
rule.</li>
<li>An integration test that starts the verifier server, performs real
provider discovery, and confirms the model count matches the actual
provider API response DOES satisfy this rule.</li>
<li>The Makefile target <code>make test-verifier-integration</code> MUST
exist and MUST run without mocks.</li>
</ul>
<p><strong>The "Tests Pass But Features Don't Work"
Guarantee</strong>:</p>
<pre><code>NO TEST MAY PASS UNLESS THE FEATURE IT TESTS IS DEMONSTRABLY USABLE
BY AN END USER IN THE SAME BUILD.</code></pre>
<ul>
<li>If <code>TestModelList</code> passes but
<code>helixcode --list-models</code> shows hardcoded data, the test is a
BLUFF.</li>
<li>If <code>TestProviderHealth</code> passes but the health endpoint
returns <code>200 OK</code> for a provider that is actually down, the
test is a BLUFF.</li>
<li>If <code>TestLLMGeneration</code> passes but
<code>--prompt "hello"</code> returns a simulated string, the test is a
BLUFF.</li>
<li>Bluff tests MUST be rewritten or deleted. There is no "grandfather"
exception.</li>
</ul>
<p><strong>Evidence Standard</strong>: Every test that claims to verify
model/provider functionality MUST:</p>
<ol type="1">
<li>Call a real API endpoint or a real verifier database</li>
<li>Assert on response content that could only come from that real
source</li>
<li>Include a test that runs the CLI binary with
<code>--list-models</code> and checks output against verifier data</li>
</ol>
<hr />
<h2 id="const-039-real-time-model-status-accuracy">CONST-039: Real-Time
Model Status Accuracy</h2>
<p><strong>Rule</strong>: Model status (available, rate-limited,
cooldown, offline, deprecated) displayed to users MUST reflect the
actual state as known by LLMsVerifier within <code>max_staleness</code>
seconds (default: 60s).</p>
<p><strong>Polling vs. Push</strong>:</p>
<ul>
<li>If WebSocket/SSE push is unavailable, the system MUST poll
LLMsVerifier at most every <code>status_poll_interval</code> (default:
30s).</li>
<li>The TUI MUST display a "last updated" timestamp with every model
listing.</li>
<li>Models in "cooldown" or "rate-limited" state MUST show the estimated
recovery time if known.</li>
</ul>
<p><strong>Accuracy Verification</strong>:</p>
<ul>
<li>Challenge script
<code>challenges/scripts/model_status_accuracy_challenge.sh</code> MUST:
<ol type="1">
<li>Artificially rate-limit a provider by exhausting its quota</li>
<li>Wait for the status to propagate to the verifier</li>
<li>Check that <code>helixcode --list-models</code> shows the
rate-limited status within 60s</li>
<li>Check that <code>SelectOptimalModel()</code> no longer selects the
rate-limited model</li>
</ol></li>
</ul>
<p><strong>Prohibition</strong>: Status indicators that are "always
green" or that lag >60s behind reality violate this rule.</p>
<hr />
<h2
id="const-040-all-providers-and-models-integration-mandate">CONST-040:
All Providers and Models Integration Mandate</h2>
<p><strong>Rule</strong>: HelixCode MUST integrate with ALL providers
and models that LLMsVerifier supports, subject only to:</p>
<ol type="1">
<li>The provider being explicitly disabled in configuration
(<code>enabled: false</code>)</li>
<li>The API key being absent and the provider requiring one</li>
<li>The provider being marked <code>deprecated</code> in the verifier
database</li>
</ol>
<p><strong>Minimum Provider Set</strong> (SHALL NOT be reduced without
constitutional amendment): | Provider | Auth Type | Required Env Var |
|----------|-----------|-----------------| | OpenAI | API Key |
<code>OPENAI_API_KEY</code> | | Anthropic | API Key / OAuth |
<code>ANTHROPIC_API_KEY</code> | | Gemini | API Key |
<code>GEMINI_API_KEY</code> | | DeepSeek | API Key |
<code>DEEPSEEK_API_KEY</code> | | Groq | API Key |
<code>GROQ_API_KEY</code> | | Mistral | API Key |
<code>MISTRAL_API_KEY</code> | | xAI | API Key |
<code>XAI_API_KEY</code> | | OpenRouter | API Key |
<code>OPENROUTER_API_KEY</code> | | Ollama | Local | None (auto-detect)
| | Llama.cpp | Local | None (auto-detect) |</p>
<p><strong>Integration Requirement</strong>: For every provider in the
minimum set:</p>
<ul>
<li>There MUST be a provider adapter file in <code>internal/llm/</code>
or <code>internal/verifier/adapters/</code></li>
<li>There MUST be a <code>*_test.go</code> file with real API tests
(skipped only if <code>HELIX_SKIP_LIVE_PROVIDER_TESTS</code> is
set)</li>
<li>There MUST be a challenge script in
<code>challenges/scripts/</code></li>
<li>The model listing MUST include models from this provider when the
provider is enabled</li>
</ul>
<hr />
<h2
id="const-041-mcp--lsp--acp--embedding--rag--skills--plugins-integration-mandate">CONST-041:
MCP / LSP / ACP / Embedding / RAG / Skills / Plugins Integration
Mandate</h2>
<p><strong>Rule</strong>: LLMsVerifier integration SHALL extend beyond
basic model listing to cover ALL capability dimensions:</p>
<ol type="1">
<li><p><strong>MCP (Model Context Protocol)</strong>: The verifier MUST
report which models support MCP tool calling. HelixCode's MCP subsystem
MUST consult verifier capability flags before selecting a model for
tool-use tasks.</p></li>
<li><p><strong>LSP (Language Server Protocol)</strong>: The verifier
MUST report code-analysis capabilities. Models without
<code>code_analysis</code> capability MUST NOT be selected for
refactoring or debugging tasks.</p></li>
<li><p><strong>ACP (Agent Capability Protocol)</strong>: The verifier
MUST report multi-agent coordination support. Models with
<code>supports_parallel_tool_use</code> MUST be preferred for ACP
workflows.</p></li>
<li><p><strong>Embedding</strong>: The verifier MUST report
<code>supports_embeddings</code> for each model. The
<code>CogneeConfig</code> embedding model selection MUST be
verifier-aware.</p></li>
<li><p><strong>RAG (Retrieval-Augmented Generation)</strong>: The
verifier MUST report context-window sizes. RAG chunking strategies MUST
adapt to the selected model's <code>context_window_tokens</code> as
reported by the verifier.</p></li>
<li><p><strong>Skills / Plugins</strong>: The verifier MUST track plugin
compatibility. Models flagged <code>plugin_compatible</code> MUST be
used when skill/plugin execution is required.</p></li>
</ol>
<p><strong>Capability Checklist</strong> (MUST be verified by
challenge):</p>
<ul class="task-list">
<li><label><input type="checkbox" />MCP tool calling verified for at
least 3 providers</label></li>
<li><label><input type="checkbox" />LSP code-analysis verified for at
least 3 providers</label></li>
<li><label><input type="checkbox" />ACP parallel tool use verified for
at least 2 providers</label></li>
<li><label><input type="checkbox" />Embedding generation verified for at
least 2 providers</label></li>
<li><label><input type="checkbox" />RAG context-window adaptation
verified</label></li>
<li><label><input type="checkbox" />Skills/plugin execution verified for
at least 2 providers</label></li>
</ul>
<p><strong>Prohibition</strong>: Capability flags MUST NOT be hardcoded.
The <code>Provider.GetCapabilities()</code> method MUST return data
sourced from the verifier's <code>VerificationResult</code> fields.</p>
<hr />
<h2 id="article-xii--repository-safety">Article XII — Repository
Safety</h2>
<h3 id="121-const-042--no-secret-leak">§12.1 (CONST-042) —
No-Secret-Leak</h3>
<p>No API key, token, password, certificate, or other credential may be
committed to any repository owned by HelixDevelopment or vasic-digital,
transitively or otherwise. All secrets live in <code>.env</code> files
(mode 0600) listed in <code>.gitignore</code>. Any leak — to git, logs,
build artefacts, screenshots, or external services — is a release
blocker until rotated and post-mortemed.</p>
<p><strong>Operational requirements:</strong></p>
<ul>
<li>Every repo must have <code>.env</code>, <code>.env.local</code>,
<code>.env.*</code> (with <code>!.env.example</code> exception),
<code>*.pem</code>, <code>*.key</code>, <code>*.crt</code>,
<code>id_rsa*</code> in <code>.gitignore</code>.</li>
<li><code>scripts/scan-secrets.sh</code> (or equivalent) must run before
every push; failing it blocks the push.</li>
<li>API keys for development are sourced from the canonical
<code>../helix_agent/.env</code> (mode 0600, never under git) and copied
— never symlinked, never committed — into per-repo <code>.env</code>
files.</li>
</ul>
<p><strong>Cascade requirement:</strong> This article must appear
verbatim in every owned-by-us repository's <code>CONSTITUTION.md</code>,
<code>CLAUDE.md</code>, and <code>AGENTS.md</code>. Owned-by-us repos
are listed in <code>scripts/owned-repos.txt</code> (or, until that file
exists, the meta-repo <code>propagate-governance.sh</code> script's
submodule walk excluding third-party trees).</p>
<h3 id="122-const-043--no-force-push">§12.2 (CONST-043) —
No-Force-Push</h3>
<p>No force push, force-with-lease push, history rewrite, branch
deletion of <code>main</code>/<code>master</code>, or
upstream-overwriting operation may be performed without explicit,
in-conversation user approval given for that specific operation.
Authorization for one push does not extend to subsequent pushes.
Bypassing hooks (<code>--no-verify</code>), signature verification
(<code>--no-gpg-sign</code>), or protected-branch rules also requires
explicit approval. This applies to every repository in the
HelixDevelopment / vasic-digital stack.</p>
<p><strong>Operational requirements:</strong></p>
<ul>
<li>Local pre-push hook at <code>scripts/git-hooks/pre-push</code>
(installed by <code>scripts/install-git-hooks.sh</code>) must reject
<code>--force</code> / <code>--force-with-lease</code> unless
<code>HELIX_FORCE_PUSH_APPROVED=1</code> is set.</li>
<li>The hook is a courtesy gate; this constitutional clause is the
actual contract.</li>
<li>Regular non-force pushes of new commits to existing branches on
already-configured remotes are PERMITTED without per-push approval,
scoped to a programme/conversation in which the user has authorised the
cadence.</li>
</ul>
<p><strong>Cascade requirement:</strong> Same as §12.1 — verbatim, every
owned-by-us repo's three governance files.</p>
<ul>
<li><code>README.md</code> — project overview, quickstart.</li>
<li><code>AGENTS.md</code> — guidance for AI coding agents (Codex,
Cursor, etc.).</li>
<li><code>CLAUDE.md</code> — guidance specifically for Claude Code.</li>
<li><code>docs/HOST_POWER_MANAGEMENT.md</code> — CONST-033 background
and runbook.</li>
</ul>
<!-- CONST-035 anti-bluff addendum (cascaded) -->
<h2
id="const-035--anti-bluff-tests--challenges-mandatory-inherits-from-root">CONST-035
— Anti-Bluff Tests & Challenges (mandatory; inherits from root)</h2>
<p>Tests and Challenges in this submodule MUST verify the product, not
the LLM's mental model of the product. A test that passes when the
feature is broken is worse than a missing test — it gives false
confidence and lets defects ship to users. Functional probes at the
protocol layer are mandatory:</p>
<ul>
<li>TCP-open is the FLOOR, not the ceiling. Postgres → execute
<code>SELECT 1</code>. Redis → <code>PING</code> returns
<code>PONG</code>. ChromaDB → <code>GET /api/v1/heartbeat</code> returns
200. MCP server → TCP connect + valid JSON-RPC handshake. HTTP gateway →
real request, real response, non-empty body.</li>
<li>Container <code>Up</code> is NOT application healthy. A
<code>docker/podman ps</code> <code>Up</code> status only means PID 1 is
running; the application may be crash-looping internally.</li>
<li>No mocks/fakes outside unit tests (already CONST-030; CONST-035
raises the cost of a mock-driven false pass to the same severity as a
regression).</li>
<li>Re-verify after every change. Don't assume a previously-passing test
still verifies the same scope after a refactor.</li>
<li>Verification of CONST-035 itself: deliberately break the feature
(e.g. <code>kill <service></code>, swap a password). The test MUST
fail. If it still passes, the test is non-conformant and MUST be
tightened.</li>
</ul>
<h2
id="const-033-clarification--distinguishing-host-events-from-sluggishness">CONST-033
clarification — distinguishing host events from sluggishness</h2>
<p>Heavy container builds (BuildKit pulling many GB of layers, parallel
podman/docker compose-up across many services) can make the host
<strong>appear</strong> unresponsive — high load average, slow SSH,
watchers timing out. <strong>This is NOT a CONST-033 violation.</strong>
Suspend / hibernate / logout are categorically different events.
Distinguish via:</p>
<ul>
<li><code>uptime</code> — recent boot? if so, the host actually
rebooted.</li>
<li><code>loginctl list-sessions</code> — session(s) still active? if
yes, no logout.</li>
<li><code>journalctl ... | grep -i 'will suspend\|hibernate'</code> —
zero broadcasts since the CONST-033 fix means no suspend ever
happened.</li>
<li><code>dmesg | grep -i 'killed process\|out of memory'</code> — OOM
kills are also NOT host-power events; they're memory-pressure-induced
and require their own separate fix (lower per-container memory limits,
reduce parallelism).</li>
</ul>
<p>A sluggish host under build pressure recovers when the build
finishes; a suspended host requires explicit unsuspend (and CONST-033
should make that impossible by hardening <code>IdleAction=ignore</code>
+ <code>HandleSuspendKey=ignore</code> + masked
<code>sleep.target</code>, <code>suspend.target</code>,
<code>hibernate.target</code>, <code>hybrid-sleep.target</code>).</p>
<p>If you observe what looks like a suspend during heavy builds, the
correct first action is <strong>not</strong> "edit CONST-033" but
<code>bash challenges/scripts/host_no_auto_suspend_challenge.sh</code>
to confirm the hardening is intact. If hardening is intact AND no
suspend broadcast appears in journal, the perceived event was
build-pressure sluggishness, not a power transition.</p>
<hr />
<h2
id="article-xi-119--anti-bluff-forensic-anchor-cascaded-from-parent-constitutionmd">Article
XI §11.9 — Anti-Bluff Forensic Anchor (cascaded from parent
CONSTITUTION.md)</h2>
<blockquote>
<p>Verbatim user mandate (2026-04-29, reasserted multiple times across
2026-05): <em>"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!"</em></p>
</blockquote>
<p>Operative rule: <strong>The bar for shipping is not "tests pass" but
"users can use the feature."</strong> Every PASS in this codebase MUST
carry positive runtime evidence captured during execution. Metadata-only
/ configuration-only / absence-of-error / grep-based PASS without
runtime evidence are critical defects regardless of how green the
summary line looks. No false-success results are tolerable.</p>
<p>This anchor MUST remain in this submodule's CONSTITUTION.md,
CLAUDE.md, and AGENTS.md alongside CONST-047 — see the parent
repository's <code>CONSTITUTION.md</code> for the full text.</p>
<hr />
<h2
id="const-048-full-automation-coverage-mandate-cascaded-from-constitution-submodule-11425">CONST-048:
Full-Automation-Coverage Mandate (cascaded from constitution submodule
§11.4.25)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-15): <em>"Make sure that every
feature, every functionality, every flow, every use case, every edge
case, every service or application, on every platform we support is
covered with full automation tests which will confirm anti-bluff policy
and provide the proof of fully working capabilities, working
implementation as expected, no issues, no bugs, fully documented, tests
covered! Nothing less than this does not give us a chance to deliver
stable product! This is mandatory constraint which MUST BE respected