@tiphys/kernel 0.0.0 → 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/assurance-modes.yaml

@@ -0,0 +1,278 @@
+# THE ASSURANCE MODE DEFINITIONS (kernel plan M3, M3-P3; R-024, R-096).
+#
+# Blueprint section 8 declares three modes and their merge authority, and adds
+# the sentence this whole document exists to make checkable: "The current
+# proven process is the definition of `full`. Downgrades are declared, never
+# improvised."
+#
+# WHAT IS DERIVED AND FROM WHERE, so no value here is a matter of taste:
+#
+#   full.pipeline    the process document's own sequence, enumerated (process
+#                    doc section 9 item 3, R-096), with `fix-round-verification`
+#                    present because T-003 made a delta review of every fix
+#                    round structural rather than discretionary.
+#   direct-pr        blueprint section 8 row 2, "implement + gates, no
+#                    adversarial layers".
+#   local-only       blueprint section 8 row 3, "implement, orchestrator diff
+#                    review, local fast-forward".
+#   gate-sets        derived from gate-registry.yaml: each mode selects the
+#                    gates whose own `modes` list names it.
+#                    `mode-gate-sets-resolve` checks that derivation in ONE
+#                    DIRECTION ONLY, and this comment used to claim it "keeps
+#                    the two files from drifting apart", which is FALSE and is
+#                    corrected here rather than left standing.
+#                    CHECKED: every entry listed here names a gate the registry
+#                      declares, and that gate's `modes` list names this mode.
+#                      So an entry that resolves to a gate which never runs in
+#                      this mode is a violation.
+#                    NOT CHECKED, and this is the open hole: the CONVERSE. A
+#                      gate the registry declares with `modes` naming this mode,
+#                      but which is ABSENT from the list below, is invisible.
+#                      The check iterates the entries present here and never
+#                      iterates the registry, so there is no code path that
+#                      could see the omission (src/checks.ts:626).
+#                      Measured: dropping `deploy` from `full` while the
+#                      registry still declares `modes: [full]` for it validates
+#                      at exit 0 with no diagnostic, and so does adding a mode
+#                      to a registry gate without adding the gate here.
+#                    CONSEQUENCE, stated so nobody has to re-derive it: this
+#                      document can UNDER-report which gates a mode runs. That
+#                      is a false description rather than a false assurance
+#                      claim, which is why it is tracked as a low rather than
+#                      fixed in place, but "one direction" and "no drift" are
+#                      not the same sentence and this file may not say the
+#                      second while meaning the first.
+#                    This is the third occurrence in one phase of a check that
+#                      constrains a relation in one direction while its own
+#                      documentation claims both. Three is a mechanism, not
+#                      three anecdotes; it is tracked in delivery/STATE.md:775.
+#   skips            derived: every stage in `full`'s pipeline that this mode's
+#                    pipeline omits, AND NOTHING ELSE.
+#                    `mode-no-undeclared-downgrade` recomputes it rather than
+#                    trusting it, and the recomputation has THREE parts because
+#                    "AND NOTHING ELSE" is measured against `full`, not against
+#                    this mode:
+#                      completeness: a stage `full` runs that this mode's
+#                        pipeline omits, and that is not declared here, is a
+#                        violation.
+#                      soundness A: a stage declared here that this mode's OWN
+#                        pipeline still runs is a violation.
+#                      soundness B: a stage declared here that `full` does not
+#                        run either is a violation, because nothing omits it
+#                        relative to the reference and it is no downgrade.
+#                    Soundness A was added after a review measured that without
+#                    it one bogus entry on `full` made `tiphys mode show` state
+#                    the opposite of the truth about this project's own
+#                    delivery, at exit 0
+#                    (delivery/review/clean-room-m3-p3-r8-criteria.md:217).
+#                    Soundness B was added a round later, after that round's
+#                    own documentation claimed the check was complete: the
+#                    stage vocabulary has thirteen ids and `full`'s pipeline
+#                    has twelve, so `direct-pr` naming `orchestrator-diff-review`
+#                    here validated at exit 0 and inflated the skipped-stage
+#                    count `tiphys mode show` prints. Shrinking `full`'s own
+#                    pipeline reaches the same violation from the other side,
+#                    editing no `skips` list at all.
+#                    ON `full` THE THREE PARTS TOGETHER MEAN ITS `skips` MUST BE
+#                    EMPTY, since an entry is either inside its own pipeline
+#                    (soundness A) or outside it (soundness B). That is not
+#                    incidental: `tiphys mode show` calls `full` the
+#                    un-downgraded process by NAME, so a `full` that quietly
+#                    became a downgrade must be refused rather than described.
+#
+# WHAT M3 NEVER RUNS, said plainly. The kernel runs `full` and only `full`; the
+# milestone exit test is a full-mode run. `direct-pr` and `local-only` are
+# witnessed here by validation and by `tiphys mode show`, never by execution.
+# Building an enforcement engine for a mode this milestone never enters is the
+# M1-P3 failure the plan is trying not to repeat.
+#
+# CONSTRAINTS C-2 AND C-3. No stage in this file is completed, detected or
+# excluded by process liveness, by a signal, or by a detached long-running
+# process. A registered test scans this file and its schema for the four
+# tokens C-2 and C-3 are written in and requires ZERO hits, which is why those
+# four tokens do not appear here even as a disclaimer. It is a fixed-token
+# presence check and nothing more: a stage whose completion were
+# liveness-detected without using any of the four words would pass it, and the
+# plan's hazard map names that residue in the open rather than papering over
+# it. The second line is the hazard review contract, which reads prose.
+
+kind: assurance-modes
+version: 1
+
+modes:
+  # ------------------------------------------------------------------
+  # full: the current proven process, which is what the word means here.
+  # ------------------------------------------------------------------
+  - id: full
+    declared-by: >-
+      blueprint section 8 (the mode and its pipeline); process doc section 9
+      item 3 enumerated (R-096); T-003 for the fix-round-verification stage;
+      DR-0012 and DR-0015 for the merge authority actually in force; DR-0016
+      for the escalation response; T-007 and D-M3-32 for the review contracts.
+    # ORDER IS LOAD-BEARING. R-024: an adversarial plan review happens before
+    # anyone builds, which is a property of this sequence and not of its set,
+    # and `mode-stage-order` is the check that says so.
+    pipeline:
+      - intake
+      - verification-pass
+      - plan
+      - adversarial-plan-review
+      - implement
+      - clean-room-review
+      - fix-round
+      # T-003's structural consequence, applied rather than asserted as new
+      # policy: full mode REQUIRES a delta review or verification of every fix
+      # round instead of leaving it to orchestrator discretion. The evidence is
+      # delivery/review/verification-m1-p3-fix-round.md.
+      - fix-round-verification
+      - merge-on-green
+      - deploy-verify
+      - migration-verify
+      - final-report
+    skips: []
+    # Every gate in gate-registry.yaml whose `modes` list contains `full`,
+    # which today is all of them.
+    gate-sets:
+      - manifest-self-check
+      - coverage
+      - credential-scrub
+      - credential-token
+      - suite
+      - citations
+      - scope
+      - deploy
+      - migrations
+      - clause-map
+      - red-witness
+      - agent-rules-drift
+      - unit-tests-for-changed-service-methods
+      - fixtures-for-changed-component-states
+    # T-007, D-M3-32. Two CONTRACTS, not two reviewers. The decorrelation that
+    # mattered on M1-P5 was in the question asked: both reviews walked all
+    # fifteen acceptance criteria and agreed on every mechanical fact, and the
+    # one briefed on hazards found a high-severity live-lock the other's report
+    # does not even name. DR-0012's requirement of two model FAMILIES is a
+    # different axis; full requires both.
+    review-contracts:
+      - criteria
+      - hazard
+    # BLUEPRINT SECTION 8'S TABLE SAYS `owner` FOR THIS ROW, AND THAT IS NOT
+    # WHAT IS IN FORCE. The owner granted delegated authority in DR-0012 and
+    # then removed themselves from the merge path entirely in DR-0015,
+    # milestone boundaries included. Declaring `owner` here would record a
+    # regime this project has left, which is precisely the drift the checks in
+    # this phase exist to prevent, and it would sit incoherently beside the
+    # escalation bounds below, which are DR-0012's own. A project that wants
+    # the blueprint's default declares `owner`; the value stays representable.
+    merge-authority: delegated-under-conditions
+    granted-by: DR-0012
+    # DR-0012, "What 'clean' means, defined here so it cannot be softened
+    # later". All six, in the record's order, not summarized.
+    conditions:
+      - >-
+        Two independent clean-room reviews exist for the current head, produced
+        on different model families, each written to `delivery/review/` and
+        committed.
+      - >-
+        Neither review carries an unresolved finding at high or medium
+        severity. Low findings may be merged with, provided each is either
+        fixed or explicitly recorded as a tracked item with a reason.
+      - >-
+        Both reviewers were given the phase's acceptance criteria as their
+        contract, and both walked or executed them. A review that only read is
+        not sufficient for a code phase.
+      - >-
+        CI is green on the exact head being merged, not on an earlier one.
+      - >-
+        The scope audit passes: changed files are on the phase's files-to-touch
+        list plus the two standing pre-authorized extras.
+      - >-
+        Where the reviews disagree, the orchestrator arbitrates with evidence
+        and records the arbitration in the merge commit or in the review file.
+        A disagreement is never resolved by preferring the more convenient
+        verdict.
+    # DR-0012's two limits with DR-0016's response. DATA THE ORCHESTRATOR BRIEF
+    # CITES, NOT AN ENFORCEMENT ENGINE: nothing in M3 counts fix rounds.
+    escalation-bounds:
+      max-fix-rounds-after-review: 2
+      recurrence-of-high-in-one-component: 1
+      on-exceeded: fresh-implementer-and-third-contract
+
+  # ------------------------------------------------------------------
+  # direct-pr: implement plus gates, no adversarial layers.
+  # ------------------------------------------------------------------
+  - id: direct-pr
+    declared-by: >-
+      blueprint section 8 row 2, "implement + gates, no adversarial layers",
+      with merge authority `owner` from the same row.
+    pipeline:
+      - intake
+      - plan
+      - implement
+      - merge-on-green
+      - final-report
+    # DECLARED, NOT IMPROVISED. Seven stages of `full` are dropped and every
+    # one of them is named here; `mode-no-undeclared-downgrade` recomputes this
+    # list from `full`'s pipeline and reddens on any omission that is not on it,
+    # and on any entry here that this mode's own pipeline still runs.
+    skips:
+      - verification-pass
+      - adversarial-plan-review
+      - clean-room-review
+      - fix-round
+      - fix-round-verification
+      - deploy-verify
+      - migration-verify
+    # Every gate whose `modes` list contains `direct-pr`: all of them except
+    # `deploy` and `migrations`, which are the two full-only entries.
+    gate-sets:
+      - manifest-self-check
+      - coverage
+      - credential-scrub
+      - credential-token
+      - suite
+      - citations
+      - scope
+      - clause-map
+      - red-witness
+      - agent-rules-drift
+      - unit-tests-for-changed-service-methods
+      - fixtures-for-changed-component-states
+    merge-authority: owner
+
+  # ------------------------------------------------------------------
+  # local-only: implement, orchestrator diff review, local fast-forward.
+  # ------------------------------------------------------------------
+  - id: local-only
+    declared-by: >-
+      blueprint section 8 row 3, "implement, orchestrator diff review, local
+      fast-forward", with merge authority "owner approves, orchestrator
+      merges", which SC-008 and plan v1 D-6 read as
+      owner-approves-orchestrator-merges.
+    pipeline:
+      - implement
+      - orchestrator-diff-review
+      - merge-on-green
+    skips:
+      - intake
+      - verification-pass
+      - plan
+      - adversarial-plan-review
+      - clean-room-review
+      - fix-round
+      - fix-round-verification
+      - deploy-verify
+      - migration-verify
+      - final-report
+    # Every gate whose `modes` list contains `local-only`.
+    gate-sets:
+      - manifest-self-check
+      - credential-scrub
+      - suite
+      - agent-rules-drift
+    # SEE THE $comment ON THIS FIELD IN THE SCHEMA. This value describes a
+    # regime the Tiphys kernel itself has left (DR-0015): for this project the
+    # owner is not an approval step anywhere in execution. It is kept because
+    # blueprint section 8 assigns it to this row and another project may want
+    # it, not because anything here runs under it.
+    merge-authority: owner-approves-orchestrator-merges