﻿SP.COMPOSITION.SYS01-v0.1.3 — START HERE / INSTALL AND VERIFY


Status: TARGET-HOST INSTALLATION GUIDE · v0.1.3 LOCATOR-CORRECTION PATCH · TARGETED MQA PASS · TEST-READY / UNPROVEN · G2 NOT RUN
Target: clean ChatGPT Project or equivalent persistent Project surface


PURPOSE
Install the minimum SYS-01 persistent core without stacking component packages or creating multiple state authorities.


INSTALLATION — ONE COHERENT MOMENT
1. Create a clean persistent Project fixture.
2. Copy the full content of `SP.COMPOSITION.SYS01-v0.1.3__PROJECT-INSTRUCTIONS__TARGET-HOST` (Drive 1xaLFoHbzpDGrlcli3IAP2ujahnaa8VqWtiuRlhZvB-U) into the Project Instructions surface.
3. Instantiate one project state from `SP.COMPOSITION.SYS01-v0.1.3__CANONICAL-STATE-TEMPLATE` (Drive 1jiRGUgEUOzL_kT1iG4oWTD76NUnrM0uKkeCZGCe_DFQ) and make that instantiated object available to the Project as `SYS01_PROJECT_STATE.md` or an equivalent uniquely designated current-state artifact.
4. Fill only the project facts required for the fixture/use case. Preserve UNKNOWN/PENDING/HOLD/CONFLICT where appropriate; do not preload expected test answers.
5. Do NOT separately install P012, P019 or P018 instruction packages. Their required behavior has already been compiled into the single SYS-01 Project Instructions payload.
6. Do NOT install P010 in this v0.1.3 edition. P010 is the alternative rescue/bootstrap path for a later existing-project variant.
7. Do NOT activate P070 or any recurring project monitor in this v0.1.3 edition.
8. Keep the exact composition manifest (Drive 1e0vFJULTr3NJebFgg-uJNEAGWuofYfwd2E4QHvZHj6o) and G2 seam protocol (Drive 1CKOVmC1yqi0GAXXk6PszEPlwgCpWOAORfCqbppmVc78) outside the runtime authority path as build/proof evidence.


ACTIVATION CHECK
In the first chat, ask: `Verificá la configuración de SYS-01 y reportá sólo lo observable antes de iniciar trabajo material.`


A correct activation report should establish, without inventing observations:
- composed Project Instructions: ACTIVE or NOT_OBSERVABLE;
- canonical state: exactly one readable state object, or MISSING/NOT_OBSERVABLE;
- P012 governing frame: active through the composed instructions;
- P019 mapping: `information_architecture` namespace is present/readable;
- P018 mapping: `delivery_control` namespace is present/readable;
- competing state authority: none observed, otherwise CONFLICT;
- P010: INACTIVE in this edition;
- P070/recurring monitor: INACTIVE in this edition;
- write capability: ACTIVE, UNAVAILABLE or NOT_OBSERVABLE — never assumed.


STOP CONDITIONS BEFORE USE
Do not treat SYS-01 as active if:
- Project Instructions are not installed/observable;
- there is no single readable canonical state;
- P019 or P018 is installed as a competing current-state ledger;
- the system claims persistent write capability that cannot be observed;
- a recurring monitor is claimed without a real configured automation.


NORMAL USE
Once activation is valid, the user should work normally. P012 remains the background governing frame. P019 activates only for information-architecture work. P018 activates only for delivery-control work. Views, specialist PM, task and artifact modules activate only when their trigger exists.


PROOF STATUS
Static package preparation does not prove runtime persistence, rehydration or integration. The clean-host seam proof is defined in `SP.COMPOSITION.SYS01-v0.1.3__G2-SEAM-PROTOCOL__LOCATOR-CORRECTION__READY-NOT-RUN` and remains NOT RUN until the General G2 lane is explicitly started for this exact edition.


CURRENT CHATGPT INSTALLATION PATH — verified 2026-09-17
For the current ChatGPT Projects surface: create the Project from `Nuevo proyecto` in the sidebar; open the Project’s three-dot menu → `Configuración del proyecto` to paste the composed Project Instructions; add the instantiated canonical state in the Project sources area as an uploaded file or supported Google Drive link when available. Project memory may support contextual continuity, but it never replaces the canonical SYS01_PROJECT_STATE. A readable Drive/source link does not imply write capability; verify writeback separately before claiming state persistence.




v0.1.1 STORAGE-ROUTING PATCH
Before normal use, confirm information_architecture.storage_architecture in the instantiated SYS01_PROJECT_STATE.
Default for a bounded Project-only fixture: mode=HOST_LOCAL_BOUNDED, p082_required=false, adapter_status=NOT_REQUIRED.
If external durable repository requirements are introduced, activate P019 and its Storage Routing Gate. Bind only an exact compatible P082 edition and record the storage manifest + operational registry refs; do not install P082 as a second semantic state authority.


Additional activation checks:
- storage mode is explicit;
- P082 is NOT_REQUIRED unless its trigger exists;
- if P082 is ACTIVE, exact provider/surface/ownership/writer model is explicit;
- if P082 is ACTIVE, registry/direct-locator retrieval is configured and no duplicate CURRENT ledger exists;
- unsupported adapter/writer model is HOLD rather than inferred compatible.


Current patch proof protocol: Drive 1CKOVmC1yqi0GAXXk6PszEPlwgCpWOAORfCqbppmVc78.




T22 INTEGRATION PATCH — 2026-10-02
Component bindings are registry-first. This compiled successor snapshots current critical component editions as follows:
P012 CURRENT locator 1LlDAa94UFyuXJpeXC6HAiar_kWA3AQxG;
P019 CURRENT locator 1PQj7AgdFW1Y0cSb1xgXRhUsB7aeUfGMj;
P018 CURRENT locator 1ck1O5zPXRE4RJNgy4VhqNzegA1szwTO6;
conditional P082 CURRENT locator 1fjoRUq36MMLSxq4GAahG_K7W126d_TCX.
Historical component file IDs remain evidence only and do not override registry CURRENT.


Canonical SYS01_PROJECT_STATE writes now require expected_state_version. Re-read the current state immediately before a material write. If the observed version differs, return WRITE_CONFLICT and do not overwrite or advance state_version.


When P082 is ACTIVE, use its v0.1.1 optimistic write/readback transaction. A physical object write without successful P082 registry update/readback is an incomplete persistence transaction and must be HOLD / REGISTRY_UPDATE_REQUIRED / RECONCILIATION_REQUIRED as applicable.


Project memory is auxiliary context only. Its mode may be default or project-only and must not be inferred from behavior; no itemized Project-memory inventory exists. It never replaces SYS01_PROJECT_STATE.


If a future temporal extension is installed in a Project, do not assume a Scheduled Task can access Project-stored files; establish a future-run-accessible source route explicitly.
