-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathCONSTITUTION.html
More file actions
6507 lines (6502 loc) · 399 KB
/
Copy pathCONSTITUTION.html
File metadata and controls
6507 lines (6502 loc) · 399 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 3.10" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>CONSTITUTION</title>
<style>
span.smallcaps{font-variant: small-caps;}
div.columns{display: flex; gap: 1.5em;}
div.column{flex: auto;}
@media screen {
div.columns{gap: min(4vw, 1.5em);}
div.column{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;}
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; }
code span.an { color: #60a0b0; font-weight: bold; font-style: italic; }
code span.at { color: #7d9029; }
code span.bn { color: #40a070; }
code span.bu { color: #008000; }
code span.cf { color: #007020; font-weight: bold; }
code span.ch { color: #4070a0; }
code span.cn { color: #880000; }
code span.co { color: #60a0b0; font-style: italic; }
code span.cv { color: #60a0b0; font-weight: bold; font-style: italic; }
code span.do { color: #ba2121; font-style: italic; }
code span.dt { color: #902000; }
code span.dv { color: #40a070; }
code span.er { color: #ff0000; font-weight: bold; }
code span.ex { }
code span.fl { color: #40a070; }
code span.fu { color: #06287e; }
code span.im { color: #008000; font-weight: bold; }
code span.in { color: #60a0b0; font-weight: bold; font-style: italic; }
code span.kw { color: #007020; font-weight: bold; }
code span.op { color: #666666; }
code span.ot { color: #007020; }
code span.pp { color: #bc7a00; }
code span.sc { color: #4070a0; }
code span.ss { color: #bb6688; }
code span.st { color: #4070a0; }
code span.va { color: #19177c; }
code span.vs { color: #4070a0; }
code span.wa { color: #60a0b0; font-weight: bold; font-style: italic; }
</style>
<style type="text/css">
table {
border-collapse: collapse;
}
table td,
table th {
border: 1px solid #cccccc;
padding: 4px 8px;
vertical-align: top;
}
tr.cell-status-obsolete > td {
background-color: #E0E0E0;
}
tr.cell-status-obsolete > td:nth-child(2),
tr.cell-status-obsolete > td:last-child {
text-decoration: line-through;
}
</style>
</head>
<body>
<header id="title-block-header">
<h1 class="title">CONSTITUTION</h1>
</header>
<h1 id="helixcode-constitution">HelixCode Constitution</h1>
<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="inherited-from-constitutionconstitution.md-helixconstitution-submodule">INHERITED
FROM constitution/Constitution.md (HelixConstitution submodule)</h2>
<p>All universal rules in <code>constitution/Constitution.md</code>
apply unconditionally to HelixCode. This project Constitution
<strong>extends</strong> those universal rules with HelixCode-specific
addenda below — it does NOT and MAY NOT weaken any universal clause.
When this Constitution disagrees with the constitution submodule, the
constitution submodule wins.</p>
<p>The constitution submodule is at <code>./constitution/</code> (added
2026-05-14 per user mandate, pinned at the upstream
<code>HelixDevelopment/HelixConstitution</code> HEAD). To locate it from
nested submodules at arbitrary depth, source
<code>constitution/find_constitution.sh</code> from the parent project
tree.</p>
<p><strong>Project remote-policy scope (revised 2026-06-03)</strong> —
Per operator decision 2026-06-03, HelixCode aligns with the universal
Constitution’s multi-upstream Git-push allowance: GitHub
(<code>vasic-digital/*</code>, <code>HelixDevelopment/*</code>), GitLab
(same), GitFlic, and GitVerse are ALL permitted as Git remotes, and
pushes target every configured upstream. This
<strong>SUPERSEDES</strong> the earlier <code>CLAUDE.md</code> §6.W
tightening that forbade GitFlic/GitVerse — that remote-provider
restriction is <strong>LIFTED</strong>. Project tightenings unrelated to
remote providers (host power management, anti-bluff, secret-leak, etc.)
remain in force.</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:
1. Write the Challenge first 2. Run it; confirm fail (it reproduces the
bug) 3. Then write the fix 4. Re-run; confirm pass 5. Commit Challenge +
fix together</p>
<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): -
<strong>Wrapper bluff</strong> - Assertions PASS but wrapper’s exit-code
logic is buggy - <strong>Contract bluff</strong> - System advertises
capability but rejects it in dispatch - <strong>Structural
bluff</strong> - File exists but doesn’t contain working code -
<strong>Comment bluff</strong> - Comment promises behavior code doesn’t
have - <strong>Skip bluff</strong> -
<code>t.Skip("not running yet")</code> without <code>SKIP-OK</code>
marker</p>
<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>scripts/anti_bluff/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: -
PostgreSQL: <code>SELECT 1</code> - Redis: <code>PING</code> - LLM
Providers: Real generation request - HTTP Services:
<code>GET /health</code> with deep checks</p>
<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: 1. Have its own Constitution.md,
CLAUDE.md, and AGENTS.md, OR 2. Have a symlink to the parent
repository’s governance files, OR 3. Have a reference comment in its
README pointing to parent governance</p>
<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: - Environment variables
(production) - <code>.env</code> files (development, in
<code>.gitignore</code>) - Vault/Secret Manager (enterprise) - Docker
secrets (containerized)</p>
<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: - Return partial results where possible - Queue operations
for retry - Inform user of degraded state - NEVER crash or hang
indefinitely</p>
<hr />
<h2 id="const-031-audit-trail">CONST-031: Audit Trail</h2>
<p>Every significant operation MUST be logged with: - Timestamp - User
identity - Operation type - Success/failure status - Resource
affected</p>
<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: - 6-month notice - Migration guide - Compatibility
shim</p>
<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): - <strong>Wrapper bluff</strong> - assertions PASS but
wrapper’s exit-code logic is buggy - <strong>Contract bluff</strong> -
system advertises capability but rejects it in dispatch -
<strong>Structural bluff</strong> - <code>check_file_exists</code>
passes but doesn’t run the test - <strong>Comment bluff</strong> -
comment promises behavior code doesn’t actually have - <strong>Skip
bluff</strong> - <code>t.Skip("not running yet")</code> without
<code>SKIP-OK: #<ticket></code> marker</p>
<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: 1. All model metadata (names, IDs, context windows,
capabilities) 2. All provider metadata (endpoints, auth types, supported
models) 3. All verification status (verified, partial, failed, pending)
4. All scoring data (overall scores, capability scores, tier rankings)
5. All rate-limit and cooldown state</p>
<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>: - The challenge script
<code>scripts/anti_bluff/verifier_hardcode_check.sh</code> MUST scan all
Go source files for hardcoded model arrays. - Any
<code>[]string{"gpt-4", "claude-3"}</code> or equivalent literal in
production code is a constitutional violation. - The only permitted
hardcoded data is the LLMsVerifier service endpoint URL and the list of
verification test types.</p>
<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>: - A unit test
that mocks the verifier client and asserts
<code>GetAvailableModels()</code> returns 3 models DOES NOT satisfy this
rule. - 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. - The Makefile target
<code>make test-verifier-integration</code> MUST exist and MUST run
without mocks.</p>
<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: 1. Call a real API endpoint or a real
verifier database 2. Assert on response content that could only come
from that real source 3. Include a test that runs the CLI binary with
<code>--list-models</code> and checks output against verifier data</p>
<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>: - If WebSocket/SSE push is
unavailable, the system MUST poll LLMsVerifier at most every
<code>status_poll_interval</code> (default: 30s). - The TUI MUST display
a “last updated” timestamp with every model listing. - Models in
“cooldown” or “rate-limited” state MUST show the estimated recovery time
if known.</p>
<p><strong>Accuracy Verification</strong>: - Challenge script
<code>challenges/scripts/model_status_accuracy_challenge.sh</code> MUST:
1. Artificially rate-limit a provider by exhausting its quota 2. Wait
for the status to propagate to the verifier 3. Check that
<code>helixcode --list-models</code> shows the rate-limited status
within 60s 4. Check that <code>SelectOptimalModel()</code> no longer
selects the rate-limited model</p>
<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: 1. The provider
being explicitly disabled in configuration (<code>enabled: false</code>)
2. The API key being absent and the provider requiring one 3. The
provider being marked <code>deprecated</code> in the verifier
database</p>
<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: - There MUST be a provider adapter file in
<code>internal/llm/</code> or <code>internal/verifier/adapters/</code> -
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) - There MUST
be a challenge script in <code>challenges/scripts/</code> - The model
listing MUST include models from this provider when the provider is
enabled</p>
<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): - [ ] MCP tool calling verified for at least 3 providers - [
] LSP code-analysis verified for at least 3 providers - [ ] ACP parallel
tool use verified for at least 2 providers - [ ] Embedding generation
verified for at least 2 providers - [ ] RAG context-window adaptation
verified - [ ] Skills/plugin execution verified for at least 2
providers</p>
<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="const-046-no-hardcoded-content-all-user-facing-text-must-be-dynamic">CONST-046:
No Hardcoded Content — All User-Facing Text Must Be Dynamic</h2>
<p><strong>Rule</strong>: NO user-facing text, prompt template, question
text, error message, label, helper text, or explanatory content may be
hardcoded as a static literal string in any source file, test file,
configuration template, script, or governance document. All such content
MUST be either: 1. Generated dynamically by an LLM at runtime based on
context (user’s language, prompt content, session state), OR 2. Loaded
from a resource file (<code>.yaml</code>, <code>.json</code>,
<code>.toml</code>) that supports i18n and can be overridden per locale,
OR 3. Composed programmatically from verifier-provided metadata or
configuration data</p>
<p><strong>Rationale</strong>: Hardcoded English-only text creates a
system that silently breaks for non-English users. A clarification
question hardcoded as “Which file has the bug?” could be asked
identically to a Japanese, Serbian, or Spanish user who specified their
request in that language — producing an incoherent, unusable experience.
Every piece of user-facing text MUST adapt to the user’s language and
context. A static string array is a constitutional violation.</p>
<p><strong>Prohibition</strong>: Static literal arrays/slices of
question text, fixed prompt templates with hardcoded English phrases,
hardcoded error messages in anything other than Go standard library
format (which uses English identifiers but is not user-facing), and
hardcoded label/display text in TUI, CLI, desktop, or mobile
interfaces.</p>
<p><strong>Examples of violations</strong>: -
<code>[]string{"Which file has the bug?", "What is the expected behavior?"}</code>
— hardcoded question bank -
<code>fmt.Sprintf("The build failed with: %s", err)</code> —
user-visible English template -
<code>tview.NewTextView().SetText("Press Enter to continue")</code> —
hardcoded UI label - <code>return "feature not implemented"</code> —
user-visible static string</p>
<p><strong>Examples of compliant patterns</strong>: - Questions
generated by <code>llm.Generate(ctx, prompt)</code> and parsed into
structured output - Labels loaded from <code>locales/en.yaml</code> with
fallback to verifier metadata - Error wrapping:
<code>fmt.Errorf("build: %w", err)</code> — identifier-based, not
user-facing prose - Dynamic formatting:
<code>s.formatMessage(ctx, key, args...)</code> — dispatches through
i18n/LLM layer</p>
<p><strong>Enforcement</strong>: <code>make lint</code> MUST include a
check that scans for hardcoded human-readable strings exceeding a length
threshold. The anti-bluff sweep command
(<code>grep -rn "simulated\|placeholder\|stub\|TODO"</code>) MUST also
flag obvious hardcoded-text patterns.</p>
<p><strong>Cascade requirement</strong>: This rule (verbatim or by
CONST-046 ID reference) MUST appear in every owned-by-us submodule’s
CONSTITUTION.md, CLAUDE.md, and AGENTS.md.</p>
<hr />
<h2 id="const-045-no-hardcoded-distribution-hosts-all-distribution-via-containers.env">CONST-045:
No Hardcoded Distribution Hosts — All Distribution Via
containers/.env</h2>
<p><strong>Rule</strong>: ALL container distribution targets SHALL be
configured exclusively through the
<code>CONTAINERS_REMOTE_HOST_N_*</code> environment variables in
<code>containers/.env</code> (N=1..100; iteration stops at first absent
<code>_NAME</code>). The containers module’s
<code>pkg/envconfig/parser.go</code> is the authoritative loader.</p>
<p><strong>Prohibition</strong>: NO distribution host (hostname, IP
address, SSH user, SSH key path, runtime, labels) may be hardcoded in
ANY HelixCode-owned source file, test file, challenge, configuration
template, script, documentation, governance document (CONSTITUTION.md,
CLAUDE.md, AGENTS.md), or any other committed artefact.</p>
<p><strong>The sole source of truth for host enrolment is
<code>containers/.env</code></strong> (gitignored, mode 0600).
<code>containers/.env.example</code> documents the format but contains
NO operative host entries. Adding, removing, or modifying a distribution
host MUST be done by editing <code>containers/.env</code> ONLY; no code
change is required or permitted.</p>
<p><strong>Audit command</strong>:
<code>grep -rn 'CONTAINERS_REMOTE_HOST_' containers/.env</code>. The
configured set at any point is whatever <code>.env</code> declares. At
rule introduction time (2026-05-07), the configured hosts are
<code>thinker.local</code>, but the rule applies to whatever set is in
<code>.env</code> at any future point.</p>
<p><strong>Testing</strong>: Non-unit tests and Challenges that require
remote distribution SHALL read <code>containers/.env</code> at runtime.
They SHALL skip (with
<code>SKIP-OK: #P{X} no remote hosts configured</code>) when
<code>CONTAINERS_REMOTE_ENABLED</code> is <code>false</code> or unset,
and SHALL use whatever hosts are configured when enabled. No test may
hardcode a host name.</p>
<p><strong>Cascade requirement:</strong> This rule (verbatim or by
CONST-045 ID reference) MUST appear in every owned-by-us submodule’s
CONSTITUTION.md, CLAUDE.md, and AGENTS.md.</p>
<hr />
<h2 id="article-xii-repository-safety">Article XII — Repository
Safety</h2>
<h3 id="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> - 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>. - <code>scripts/scan-secrets.sh</code> (or
equivalent) must run before every push; failing it blocks the push. -
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.</p>
<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="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> - 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. - The hook is a
courtesy gate; this constitutional clause is the actual contract. -
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.</p>
<p><strong>Cascade requirement:</strong> Same as §12.1 — verbatim, every
owned-by-us repo’s three governance files.</p>
<hr />
<h2 id="article-xiii-programme-continuity">Article XIII — Programme
Continuity</h2>
<h3 id="const-044-continuation-document-maintenance-mandate">§13.1
(CONST-044) — Continuation Document Maintenance Mandate</h3>
<p>The <code>docs/CONTINUATION.md</code> document MUST be maintained in
sync with the actual state of the CLI-Agent Fusion programme at all
times. It is the authoritative resumption record for any CLI agent or
LLM picking up the work from any session, at any time.</p>
<p><strong>Mandate:</strong> Every commit that advances programme state
— feature task completion, feature close-out, push to remotes,
known-issue discovery, deferred-item resolution, phase transition,
addition or removal of submodules / remotes — MUST update
<code>docs/CONTINUATION.md</code> to reflect the new state in the same
commit (or in an immediately-following commit if the state-changing
commit is small and topical).</p>
<p><strong>Definition of “out-of-sync”:</strong> -
<code>Last updated</code> SHA in CONTINUATION ≠
<code>git rev-parse HEAD</code> on <code>main</code>. -
<code>Active feature in flight</code> in CONTINUATION ≠ feature in
<code>docs/improvements/PROGRESS.md</code> “Current focus”. - Tasks
marked done in CONTINUATION ≠ ticked tasks in <code>PROGRESS.md</code>.
- Known-issue list missing a documented failure that exists in evidence
files (<code>docs/improvements/0[5-9]_phase_*_evidence.md</code>). -
Repository state table missing or stale-SHA for any submodule listed in
<code>.gitmodules</code>.</p>
<p><strong>Severity:</strong> Out-of-sync <code>CONTINUATION.md</code>
is a <strong>CRITICAL DEFECT</strong>. Same severity as a false-success
test result under CONST-035 / Article XI §11.9. A green build with an
out-of-sync continuation document is unshippable.</p>
<p><strong>Verification:</strong>
<code>scripts/verify_continuation_sync.sh</code> (TBD; planned for Phase
3) compares CONTINUATION fields against <code>PROGRESS.md</code>,
<code>git rev-parse HEAD</code>, evidence files, and
<code>.gitmodules</code>. Non-zero exit = sync violation → blocking
pre-push.</p>
<p><strong>Cascade requirement:</strong> This article must appear
verbatim — or be referenced by <code>CONST-044</code> ID with a pointer
back to this anchor — in every owned-by-us repository’s
<code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Submodules without their own
<code>docs/CONTINUATION.md</code> reference the meta-repo’s CONTINUATION
as the authoritative document; submodules that maintain their own
CONTINUATION must pin its SHA and update on every state-changing commit
identically.</p>
<hr />
<h2 id="const-047-recursive-submodule-application-mandate">CONST-047:
Recursive Submodule Application Mandate</h2>
<blockquote>
<p><strong>Verbatim user mandate (2026-05-14):</strong> <em>“Make sure
all work we do is applied ALWAYS to all Submodules we control under our
organizations (vasic-digital and HelixDevelopment) fully recursively
everywhere with full bluff-proofing and comprehensive documentation,
user manuals and guides and full tests and Challenges
coverage!”</em></p>
</blockquote>
<p><strong>Operative rule:</strong> Every engineering deliverable
produced for HelixCode MUST be applied — fully and recursively — to
every owned submodule under the <code>vasic-digital</code> and
<code>HelixDevelopment</code> GitHub organizations. “Owned” means any
submodule whose remote URL is
<code>git@github.com:vasic-digital/*.git</code> or
<code>git@github.com:HelixDevelopment/*.git</code> (including the
<code>HelixDevelopment-s-Code/*</code> brand variant). Each such
submodule MUST receive in lockstep:</p>
<ol type="1">
<li><p><strong>Anti-bluff posture (CONST-035 / Article XI
§11.9):</strong> every test and Challenge in the submodule must
guarantee real, end-user-usable functionality. Metadata-only /
absence-of-error / fake-PASS results are critical defects in submodules
just as in the meta-repo.</p></li>
<li><p><strong>Comprehensive documentation:</strong> README plus user
manuals plus guides that match the submodule’s actual current
capabilities. Documentation that advertises features the code doesn’t
deliver is the same class of defect as a fake-PASS test.</p></li>
<li><p><strong>Full tests AND Challenges coverage:</strong> unit tests
where applicable, Challenges that exercise real workflows with captured
runtime evidence (per CONST-035). 100% of user-reachable surfaces must
be covered.</p></li>
<li><p><strong>Recursive propagation:</strong> when an owned submodule
itself depends on sub-submodules under <code>vasic-digital</code> or
<code>HelixDevelopment</code>, the mandate cascades. A submodule that
owns child submodules under our organizations is responsible for
cascading the mandate to them.</p></li>
<li><p><strong>Synchronized commits:</strong> when a meta-repo commit
advances state that touches a submodule’s surface, the corresponding
submodule commit MUST land in the same engineering session and be pushed
to all configured remotes.</p></li>
</ol>
<p><strong>Owned submodule baseline</strong> (direct children of the
meta-repo as of 2026-05-14): <code>vasic-digital/Containers</code>,
<code>vasic-digital/Security</code>,
<code>vasic-digital/Challenges</code>,
<code>vasic-digital/LLMsVerifier</code>,
<code>vasic-digital/Models</code>,
<code>HelixDevelopment/HelixQA</code>,
<code>HelixDevelopment/DocProcessor</code>,
<code>HelixDevelopment/LLMOrchestrator</code>,
<code>HelixDevelopment/LLMProvider</code>,
<code>HelixDevelopment/VisionEngine</code>,
<code>HelixDevelopment/HelixAgent</code>,
<code>HelixDevelopment-s-Code/Website</code>. Plus any nested submodule
under these orgs (full recursion).</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>CONST-047</code> ID reference) MUST appear in every owned
submodule’s <code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Non-compliance is a release blocker — same
severity as a CONST-035 bluff or a CONST-044 out-of-sync
CONTINUATION.</p>
<p><strong>Verification:</strong>
<code>scripts/verify-governance-cascade.sh</code> MUST be extended to
confirm CONST-047 anchor presence in every owned submodule (in addition
to its existing CONST-035 checks). A submodule missing the anchor is
treated identically to one missing the anti-bluff anchor: blocked from
merge.</p>
<hr />
<h2 id="const-048-full-automation-coverage-mandate-cascaded-from-constitution-submodule-11.4.25">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
without ignoring, skipping, slacking or forgetting it!”</em></p>
</blockquote>
<p>No feature / functionality / flow / use case / edge case / service /
application on any supported platform of HelixCode may be considered
deliverable until covered by automation tests proving six invariants:
(1) anti-bluff posture (CONST-035) with captured runtime evidence; (2)
proof of working capability end-to-end on target topology (no mocks
beyond unit tests — see CONST-050); (3) implementation matches
documented promise; (4) no open issues/bugs surfaced — cross-checked
against §11.4.15 / §11.4.16 trackers; (5) full documentation in sync per
§11.4.12; (6) four-layer test floor per §1 (pre-build + post-build +
runtime + paired mutation).</p>
<p>Consuming projects MUST publish a coverage ledger (feature × platform
× invariant-1..6 × status) regenerated as part of the release-gate
sweep. Gaps tracked per §11.4.15 (<code>UNCONFIRMED:</code> /
<code>PENDING_FORENSICS:</code> / <code>OPERATOR-BLOCKED:</code> with
§11.4.21 audit) — rows that quietly omit a platform are CONST-048
violations.</p>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>CONST-048</code> ID reference) MUST appear in every owned
submodule’s <code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Severity-equivalent to a §11.4 PASS-bluff at the
release-gate layer. No escape hatch. See constitution submodule
<code>Constitution.md</code> §11.4.25 for the full mandate.</p>
<h2 id="const-049-constitution-submodule-update-workflow-mandate-cascaded-from-constitution-submodule-11.4.26">CONST-049:
Constitution-Submodule Update Workflow Mandate (cascaded from
constitution submodule §11.4.26)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-15): <em>“Every time we add something
into our root (constitution Submodule) Constitution, CLAUDE.MD and
AGENTS.MD we MUST FIRST fetch and pull all new changes / work from
constitution Submodule first! All changes we apply MUST BE commited and
pushed to all constitution Submodule upstreams! In case of conflict, IT
MUST BE carefully resolved! Nothing can be broken, made faulty,
corrupted or unusable! After merging full validation and verification
MUST BE done!”</em></p>
</blockquote>
<p>Before ANY modification to <code>constitution/Constitution.md</code>,
<code>constitution/CLAUDE.md</code>, or
<code>constitution/AGENTS.md</code>, the agent or operator MUST execute
the following 7-step pipeline in order:</p>
<ol type="1">
<li><strong>Fetch + pull first</strong> inside the constitution
submodule worktree — every configured remote fetched, then
<code>git pull --ff-only</code> (or <code>--rebase</code> if non-FF;
NEVER <code>--strategy=ours</code> /
<code>--allow-unrelated-histories</code> without explicit
authorization).</li>
<li><strong>Apply the change</strong> with §11.4.17 classification +
verbatim mandate quote.</li>
<li><strong>Validate before commit</strong> —
<code>meta_test_inheritance.sh</code> (or equivalent), no merge-conflict
markers, cross-file consistency.</li>
<li><strong>Commit + push to ALL upstreams</strong> — governance files
only (NEVER <code>git add -A</code>); push to every configured remote.
One-upstream commit = CONST-049 violation (also CONST-038/§6.W and
§2.1).</li>
<li><strong>Conflict resolution</strong> preserving union of governance
content. Force-push to bypass conflicts is FORBIDDEN (CONST-043 /
§9.2).</li>
<li><strong>Post-merge validation</strong> —
<code>git submodule update --remote --init</code> + re-run cascade
verifier (CONST-047) confirming the new clause reaches every owned
submodule.</li>
<li><strong>Bump consuming project pointer</strong> —
<code>.gitmodules</code>-tracked submodule pointer advanced to the new
constitution HEAD in the SAME commit as cascade work.</li>
</ol>
<p><strong>Cascade requirement:</strong> This anchor (verbatim or by
<code>CONST-049</code> ID reference) MUST appear in every owned
submodule’s <code>CONSTITUTION.md</code>, <code>CLAUDE.md</code>, and
<code>AGENTS.md</code>. Severity-equivalent to a force-push without
CONST-043 / §9.2 authorization. No escape hatch. See constitution
submodule <code>Constitution.md</code> §11.4.26 for the full
mandate.</p>
<h2 id="const-050-no-fakes-beyond-unit-tests-100-test-type-coverage-mandate-cascaded-from-constitution-submodule-11.4.27">CONST-050:
No-Fakes-Beyond-Unit-Tests + 100%-Test-Type-Coverage Mandate (cascaded
from constitution submodule §11.4.27)</h2>
<blockquote>
<p>Verbatim user mandate (2026-05-15): <em>“Mocks, stubs, placeholders,
TODOs or FIXMEs are allowed to exist ONLY in Unit tests! All other test
types MUST interract with real fully implemented System! No fakes, empty
implementations or bluffing is allowed of any kind! All codebase of the
project MUST BE 100% covered with every supported test type: unit tests,
integration tests, e2e tests, full automation tests, security tests,
ddos tests, scaling tests, chaos tests, stress tests, performance tests,
benchmarking tests, ui tests, ux tests, Challenges (fully incorporating
our Challenges Submodule — https://github.com/vasic-digital/Challenges).
EVERYTHING MUST BE tested using helix_qa (fully incorporating helix_qa
Submodule — https://github.com/HelixDevelopment/HelixQA). helix_qa MUST
BE used with all possible written tests suites (test banks) for every
applications, service, platform, etc and execution of the full helix_qa
QA autonomous sessions! All required dependency Submodules MUST BE added
into the project as well (fully recursive!!!).”</em></p>
</blockquote>
<p>Two cooperating invariants:</p>
<p><strong>(A) No-fakes-beyond-unit-tests.</strong> Mocks, stubs, fakes,
placeholders, <code>TODO</code>, <code>FIXME</code>, “for now”, “in
production this would”, or empty-implementation patterns are PERMITTED
only in unit-test sources (<code>*_test.go</code> files invoked without
the integration build tag; <code>helix_code/tests/unit/</code>; etc.).
Every other test type — integration, E2E, full automation, security,
DDoS, scaling, chaos, stress, performance, benchmarking, UI, UX,
Challenges, helix_qa — MUST exercise the real, fully implemented
HelixCode system against real infrastructure (real PostgreSQL, real
Redis, real LLM endpoints, real containers, real captured devices).
Production code (anything under <code>helix_code/cmd/</code>,
<code>helix_code/applications/</code>,