mptyl/ThothII
1
0
Fork 0
Code Issues 25 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

docs: record P1.1 automated acceptance

Browse Source
This commit is contained in:
marcopan
2026-08-11 16:32:22 +02:00
parent eac472011e
commit da448a3166
1 changed files with 38 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PROJECT_STATE.md
+38 -1
View File
@@ -3,7 +3,44 @@
> Starting-point snapshot for new sessions. Last updated: 2026-08-10 (final verification).
> Point a fresh session here ("read PROJECT_STATE.md") before substantial work.
## P1 configuration process — ACCEPTED 2026-08-10
### P1.1 workspace-directory registry — automated integration PASS, manual PENDING (2026-08-11)
- **Scope:** P1 correction (not preprocessing). Root curator-owned catalog `thoth-workspaces.yaml`;
one self-contained directory per workspace (`<id>/workspace.yaml`, optional `<id>/evidence/**`);
generated docs stay API-owned under `workspace-docs/<id>`; internal immutable snapshots remain
flat (`<snapshots>/<commit>/<id>.yaml`) to preserve session pins and runtime trust.
- **Ownership:** the API may create a descriptor once when its catalog slot exists and the
descriptor Git object is absent at the exact base commit. Existing descriptors and curated
content are curator-owned and change only through Git commit/push then installation pull.
Update/delete publish payloads are refused as HTTP 409 `workspace_curator_owned`. Catalog and
Evidence are never written/staged/cleaned by the API. Explicit pull may produce one deterministic
docs-only follow-up commit that never touches curator bytes.
- **Schema/UI:** schema v3 remains the only descriptor schema; filesystem Evidence URI is exactly
`<id>/evidence`. Browser workspace management is read-only for ready workspaces (Pull/Sync,
Validate, installation Test, Export, Evidence summary, curator Git guidance) and offers an
editable bootstrap form only for `configuration_required` catalog slots.
- **Retained evidence:** `.artifacts/p11-integration/p11-ac0b047024fb09eeca218512526a6b23/`
(`report.json` sha256 `44250145fede36de5de941262beb833c920e8c73366d987cdd738856aac6f6d6`),
19/19 checks PASS, bound to clean source commit
`eac472011e465c24572d9a6bae14de0fb3e246c0` / tree `4fd15ec28d3b7967b7b8757158013307fb20f3b9`.
- **Verification:** backend Vitest **634 passed / 41 files** + tsc + build; frontend Vitest
**364 passed / 54 files** + tsc + build; harness focused Evidence/config pytest **39 passed**;
install-docs and schema-v3-only gates PASS; `workspace-registry-smoke.sh` and
`unified-deployment-smoke.sh` full Docker runs PASS with exact cleanup.
- **Known limitations:** P2–P6 plans/designs are unchanged and their old source paths are
inventoried for a later owner-approved adaptation plan. Windows Docker startup and native
PowerShell contract were not executed on a Windows host. P1's accepted historical evidence and
process artifacts remain untouched; the old P1 process commands are not rerunnable against the
superseding P1.1 repository contract.
- **Manual gate:** `.artifacts/manual-acceptance/p11/` is prepared for the reviewer;
follow `docs/testing/p11-manual-acceptance.md`. Project state remains:
```text
P1.1 automated integration: PASS
P1.1 manual acceptance: PENDING
```
# P1 configuration process — ACCEPTED 2026-08-10
- Retained evidence: `.artifacts/p1-integration/p1-038bf31360180dc831220b33fbadcfe6/report.md`
- Final report hashes: `report.json` `f07d49097966de6f0307490089fdb2ae61379c04b7fc7177d3c44cf001e1b46a`; `report.md` `09b6a9e9ad9eed2b049e286af452e12fa1f3174ea8d633253542604470890c6c`.