@llblab/pi-state-flow 1.0.0 → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,11 @@
|
|
|
4
4
|
|
|
5
5
|
## Unreleased
|
|
6
6
|
|
|
7
|
+
## 1.0.1: Documentation Ownership
|
|
8
|
+
|
|
9
|
+
- `Rule owners`: The documentation index now names the single owning page for each rule area, so a rule change lands in one place instead of being restated across contracts. Retired-format guidance elsewhere links to the owning page.
|
|
10
|
+
- `Stale 0.x wording removed`: Index, migration and scope-selection pages no longer claim that `contract`/`working` conversion is still available; they state the 1.0.0 rule that retired cohorts are refused and recovering one needs a State Flow 0.x acceptance first.
|
|
11
|
+
|
|
7
12
|
## 1.0.0: Automatic Recovery, No Legacy Conversion
|
|
8
13
|
|
|
9
14
|
- `Visible self-healing`: An owner whose canonical files cannot be decoded, or a boundary whose session memory is missing, no longer blocks forever. After a failed acquisition, State Flow quarantines the exact bytes privately in `<store>-quarantine/`, resets only that owner to empty memory, retries once and tells the operator, the model and the local log. Healthy owners stay untouched; filesystem, lock, cancellation and foreign-identity failures stay fail-closed.
|
package/dist/package.json
CHANGED
package/docs/README.md
CHANGED
|
@@ -16,7 +16,7 @@ Start with the [project README](../README.md) for installation and the memory mo
|
|
|
16
16
|
- [Session performance](performance.md): Run synthetic benchmarks, interpret their metrics and understand the current cost model. No provider-cache or latency guarantees.
|
|
17
17
|
- [Temporal acceptance](temporal-acceptance.md): Find the tests that witness each required property, including cancellation, ownership and replay.
|
|
18
18
|
- [Semantic handoff contract](semantic-handoff-contract.md): Current Intents / Strategy / Tactics meanings and ownership, the offline-bundle patch corpus and explicitly historical M0 preservation evidence. Deterministic acceptance is not live-model quality evidence.
|
|
19
|
-
- [Semantic compatibility decision](semantic-compatibility-decision.md): Shipped semantic migration/support policy, translation oracle, public API impact and historical writer-fence evidence. Core v3 and external-module v4 share Strategy/Tactics;
|
|
19
|
+
- [Semantic compatibility decision](semantic-compatibility-decision.md): Shipped semantic migration/support policy, translation oracle, public API impact and historical writer-fence evidence. Core v3 and external-module v4 share Strategy/Tactics; since 1.0.0 retired v1/v2 cohorts are refused with an actionable message and both retired root names stay reserved.
|
|
20
20
|
- [Scope selection contract](scope-selection-contract.md): Completed [M2 functional boundary](scope-selection-contract.md#m2-functional-acceptance-boundary): seven-selection capture/native runtime, public controls and mode-only optional presentation, with explicit legacy/private proof and operator-inspection limits. Policy data alone grants no memory.
|
|
21
21
|
- [Single-owner model interface](single-scope-interface-contract.md): Reviewed schema/canonical/native flat tools, protocol/Skills and typed runtime outputs; original-request/foreign-provenance counterexamples, deterministic linked-task/identity checkpoint and actual SDK byte measurements. No live model-quality, token/cache/cost or universal-access claim.
|
|
22
22
|
- [Public semantic modules](public-module-contract.md): Published `./modules` API since 0.27.0: native-host registration, trusted callbacks, metadata v4 retention, external-root tools, Active/Passive context and atomic Active producers. Owns public integration and currentness boundaries, not dynamic loading or sandboxing.
|
|
@@ -25,6 +25,24 @@ Start with the [project README](../README.md) for installation and the memory mo
|
|
|
25
25
|
- [Semantic extensibility decision](semantic-extensibility-decision.md): Historical accepted M5 no-new-API decision and atomic-validation countercase. Later explicitly authorized internal/public module work shipped in 0.27.0; no dynamic loader, sandbox, production archive or quality claim follows.
|
|
26
26
|
- [Semantic memory evaluation](semantic-memory-evaluation.md): Fixed linked-task trial, controlled fixture, independent rubric, isolation/measurement contract and historical credential-safe preflight. Functional implementation has shipped; live-model comparison remains separately authorization-gated and unrun.
|
|
27
27
|
|
|
28
|
+
## Rule owners
|
|
29
|
+
|
|
30
|
+
Each rule has one owning document. Other pages link to it instead of restating it, so a change lands in one place and cannot drift.
|
|
31
|
+
|
|
32
|
+
| Rule | Owner |
|
|
33
|
+
| --- | --- |
|
|
34
|
+
| Modes, configuration, lifecycle commands, storage recovery, self-healing, diagnostics | [usage.md](usage.md) |
|
|
35
|
+
| Per-file recovery rules, durability limit and the transaction rule | [filesystem-recovery.md](filesystem-recovery.md) |
|
|
36
|
+
| Canonical scope format admission, retired versions and required host packages | [compatibility.md](compatibility.md) |
|
|
37
|
+
| Semantic migration history and the settled support policy | [semantic-compatibility-decision.md](semantic-compatibility-decision.md) |
|
|
38
|
+
| Scope selection capture, native policy proof and operator inspection | [scope-selection-contract.md](scope-selection-contract.md) |
|
|
39
|
+
| Temporal lineage, causal identities, storage transactions, Pi lifecycle | [architecture.md](architecture.md) |
|
|
40
|
+
| Fork copy limits | [fork-contract.md](fork-contract.md) |
|
|
41
|
+
| Public module registration and retention | [public-module-contract.md](public-module-contract.md) |
|
|
42
|
+
| Packaged Skill guidance for the model | [../skills](../skills) |
|
|
43
|
+
|
|
44
|
+
Release chronology belongs to [CHANGELOG.md](../CHANGELOG.md), never to a rule statement.
|
|
45
|
+
|
|
28
46
|
## Development policy
|
|
29
47
|
|
|
30
48
|
- [Agent contract relocation ledger](agent-contract-relocation.md): Audit map from [AGENTS.md](../AGENTS.md) development instructions to their owning contracts and tests. It is provenance evidence, not a user guide or an open-work list.
|
|
@@ -738,7 +738,7 @@ The native seven-selection bridge, public scope controls and mode-only optional
|
|
|
738
738
|
- **Lifecycle v1:** It has no accepted excluded-owner witness skeleton. Safe admission requires the complete three-owner semantic/provenance cohort plus config/runtime (the full 11-file proof) before projection. An excluded body's corruption can therefore reject v1 admission. Only owned acceptance with verified exact-byte backup can upgrade; excluded owners remain byte-identical. No selective parser pretends this legacy dependency disappeared.
|
|
739
739
|
- **Lifecycle v2:** Only selected semantic bodies/provenance plus config/runtime are opened for ordinary selected admission. Acquired excluded Session still requires regular-file/path-chain presence of its private triple, not body reads; unacquired/deferred targets require absence. Retained private causal proof stays lifecycle metadata and cannot be invented by mode changes, observation or missing files.
|
|
740
740
|
- **Explicit operator inspection:** Current Telegram buttons/help follow wanted participation, not sparse availability. Effective is offered only for2+ owners and reads only that selected overlay; selected shared-only inspection does not require excluded Session bodies. Session/current proof still fails closed, and lifecycle-v1 admission retains its complete-cohort dependency. Disposable Off reads publish/install nothing, clear no fence and grant no private acquisition. This is not automatic Off memory access or a confidentiality promise.
|
|
741
|
-
- **Unsupported/foreign evidence:** Unknown epochs, malformed identity/selection/causal proof, old low-level writers without the supported fence and working-store migration are not repaired by this checkpoint. The [settled support policy](semantic-compatibility-decision.md#implementation-direction-and-reserved-names)
|
|
741
|
+
- **Unsupported/foreign evidence:** Unknown epochs, malformed identity/selection/causal proof, old low-level writers without the supported fence and working-store migration are not repaired by this checkpoint. The [settled support policy](semantic-compatibility-decision.md#implementation-direction-and-reserved-names) owns the current rule: retired roots stay reserved, v1/v2 cohorts are refused since 1.0.0, and recovering one needs a State Flow 0.x acceptance first.
|
|
742
742
|
|
|
743
743
|
### Current scope-aware presentation
|
|
744
744
|
|
|
@@ -158,7 +158,7 @@ Native `classifyScopeStream` (and therefore `parseScopeStream`/`loadScopeStream`
|
|
|
158
158
|
- Do not insert invalid old-plane sentinel values, materialized nulls, duplicated semantic aliases, or new hidden memory just to trip an older validator.
|
|
159
159
|
- An owner-format fence must survive unknown metadata siblings, sparse state, absent provenance registries, and the first target write. Off, inspection and runtime-only mode persistence cannot convert. An accepted owned Start transaction can; a UI receipt or pure policy choice alone grants no publication authority.
|
|
160
160
|
|
|
161
|
-
**Supported boundary:** Upgrade/quiesce all cooperating writers; unsafe low-level mixed-version clients are not supported. If a deployment requires coexistence with one, do not convert that store without a separately reviewed bridge/representation. Broad implementation authorization does not authorize exact-store rollout.
|
|
161
|
+
**Supported boundary:** Upgrade/quiesce all cooperating writers; unsafe low-level mixed-version clients are not supported. If a deployment requires coexistence with one, do not convert that store without a separately reviewed bridge/representation. Broad implementation authorization does not authorize exact-store rollout. Retired-root reservations and explicit unsupported-version refusal remain; recovering a v1/v2 store needs one State Flow 0.x acceptance first (see the [settled support policy](#implementation-direction-and-reserved-names)).
|
|
162
162
|
|
|
163
163
|
## Public API impact inventory
|
|
164
164
|
|