hachure 0.1.0 → 0.2.0

package/README.md

@@ -14,17 +14,17 @@ npm i -D hachure
 ```
 
 The package ships the normative JSON schemas, conformance test vectors, and the
-`STATUS_FUNCTION_VERSION` constant that ties implementations to a specific
+`statusFunctionVersion` constant that ties implementations to a specific
 algorithm revision.
 
 **Claiming conformance:** run the test vectors from `testVectors` against your
 implementation. For each vector, call your status-derivation function with
 `vector.input` and `vector.now`, then assert that the derived status for every
 claim ID matches `vector.expect.statusByClaimId`. Passing all vectors for a given
-`STATUS_FUNCTION_VERSION` is the bar for a conforming implementation.
+status function version is the bar for a conforming implementation.
 
 ```js
-import { testVectors, STATUS_FUNCTION_VERSION } from 'hachure';
+import { testVectors, statusFunctionVersion } from 'hachure';
 
 for (const { name, vector } of testVectors) {
   const results = deriveStatuses(vector.input, new Date(vector.now));
@@ -36,7 +36,6 @@ for (const { name, vector } of testVectors) {
 
 ---
 
-
 ## What this is
 
 Hachure is an open format for portable trust state. It defines how claims about
@@ -74,8 +73,8 @@ Resource Shape envelope. Product-specific records use product-scoped namespaces
 Pre-1.0: the format uses hard breaking changes rather than compatibility aliases.
 No forward or backward compatibility guarantees are made across versions. Version
 bumps are reflected in `schemaVersion` (an integer field in TrustBundle, currently
-`3`) and in `STATUS_FUNCTION_VERSION` (a string exported by the reference
-implementation, currently `"1"`).
+`3`) and in the status function version (a string exported by the reference
+implementation as `statusFunctionVersion`, currently `"1"`).
 
 ---
 

package/index.mjs

@@ -2,15 +2,15 @@
  * hachure — canonical npm distribution of the Hachure trust format spec.
  *
  * Exports:
- *   STATUS_FUNCTION_VERSION  — spec-side declaration of the current status
- *                               derivation algorithm version. Reference
- *                               implementations must export a matching value.
- *   schemas                  — Map<recordName, parsedSchemaObject> for every
- *                               normative schema shipped with this package.
- *   testVectors              — Array<{name, vector}> of all conformance test
- *                               vectors. Each vector has `input`, `expect`, and
- *                               `now` fields; run them against your implementation
- *                               to claim conformance.
+ *   statusFunctionVersion  — spec-side declaration of the current status
+ *                             derivation algorithm version. Reference
+ *                             implementations must export a matching value.
+ *   schemas                — Map<recordName, parsedSchemaObject> for every
+ *                             normative schema shipped with this package.
+ *   testVectors            — Array<{name, vector}> of all conformance test
+ *                             vectors. Each vector has `input`, `expect`, and
+ *                             `now` fields; run them against your implementation
+ *                             to claim conformance.
  */
 
 import { readFileSync, readdirSync } from 'node:fs';
@@ -24,7 +24,7 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
 // Any implementation claiming conformance at this version must produce the
 // same status outputs as the test vectors for all cases in conformance/.
 // ---------------------------------------------------------------------------
-export const STATUS_FUNCTION_VERSION = '1';
+export const statusFunctionVersion = '1';
 
 // ---------------------------------------------------------------------------
 // Schemas — Map of record name (filename without .schema.json) → parsed JSON.

package/interop-in-toto.md

@@ -124,7 +124,7 @@ A Kontour `TrustBundle` adds **living status** on top:
 |---|---|
 | Status is sealed at signing time. | Status is recomputed from events at query time: `f(claim, events, policy, now)`. |
 | Tamper-evident; content cannot change. | Append-only; new events and evidence accumulate. |
-| Verifier trusts the signer's identity. | Verifier trusts the derivation algorithm (`STATUS_FUNCTION_VERSION`). |
+| Verifier trusts the signer's identity. | Verifier trusts the derivation algorithm (`statusFunctionVersion`). |
 | Useful for supply-chain audits and legal holds. | Useful for operational dashboards, gates, and consumer inquiries. |
 
 The two are complementary: embed the bundle in an in-toto envelope to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hachure",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "Hachure — canonical distribution of the open trust format: normative JSON schemas, conformance test vectors, and spec constants.",
   "type": "module",
   "main": "./index.mjs",

package/status-function.md

@@ -1,7 +1,7 @@
 # Status Derivation — Specification
 
 **Function:** `status = f(claim, evidence, events, policy, authorityTrace, now)`
-**Version constant:** `STATUS_FUNCTION_VERSION` (currently `"1"`)
+**Version constant:** `statusFunctionVersion` (currently `"1"`)
 **Source of truth:** `src/status.ts` in `@kontourai/surface`
 
 ---
@@ -9,7 +9,7 @@
 ## Principle
 
 Claim status is a pure, versioned, deterministic function (ADR 0003 §7). Given the
-same inputs and the same `STATUS_FUNCTION_VERSION`, any conforming implementation
+same inputs and the same status function version, any conforming implementation
 must derive the same status. There is no stored status field that overrides
 computation; the derived status is always recomputed from the input bundle at
 evaluation time.
@@ -20,7 +20,7 @@ no clock-tick events and no background expiry.
 
 Reproducibility guarantee: if two independent implementations receive the same
 `(claim, evidence, events, policies, authorityTrace, now)` and the same
-`STATUS_FUNCTION_VERSION`, they must return the same `TrustStatus`.
+status function version, they must return the same `TrustStatus`.
 
 ---
 
@@ -214,12 +214,12 @@ From weakest to strongest: `unknown` < `rejected` < `superseded` < `disputed` <
 
 ## Versioning
 
-`STATUS_FUNCTION_VERSION` is a string exported by `@kontourai/surface`. It is
+`statusFunctionVersion` is a string exported by `@kontourai/surface`. It is
 incremented when the algorithm changes in a way that could produce different outputs
 for the same inputs. `InquiryRecord.statusFunctionVersion` captures which version
 was active at resolution time, enabling re-evaluation when the algorithm version
 changes.
 
-Conforming implementations must declare which `STATUS_FUNCTION_VERSION` value they
+Conforming implementations must declare which status function version value they
 implement. Implementations claiming version `"1"` must satisfy all conformance
 cases in `spec/conformance/`.