@awebai/oats 0.24.0 → 0.24.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.
@@ -59,5 +59,5 @@ or source checkout.
59
59
  - Partial or unknown historical evidence is inspectable but never executable.
60
60
  - No unattended approval, background refresh, or automatic advancement exists.
61
61
 
62
- Use **oats-portable-setup** to create a new preparation transaction. Use
63
- **oats-portable** to invoke the resulting exact record.
62
+ Use `oats prepare --help` for new preparation inputs and **oats-portable** to
63
+ invoke the resulting exact record.
@@ -1,69 +0,0 @@
1
- ---
2
- name: oats-portable-setup
3
- description: >-
4
- Use when preparing a source-complete portable soul for a fresh deployment,
5
- selecting a workspace-advertised import, or reasoning about source,
6
- deployment, work target, team, adoption, and provider-binding inputs. Triggers:
7
- "oats prepare", "portable setup", "import soul by reference", "fresh OATS
8
- deployment". Do not use legacy oats-config.yaml cascading as portable policy.
9
- ---
10
-
11
- # Preparing portable souls
12
-
13
- Portable preparation has two policy authorities and one resolver:
14
-
15
- 1. The soul supplies intrinsic hard requirements and rebindable defaults.
16
- 2. The workspace supplies admission, workspace defaults, imports/adoption,
17
- stores, team references, and catalogs.
18
- 3. Explicit operator choices may rebind defaults and bindings but cannot erase
19
- hard requirements.
20
-
21
- There is no repository-default tier and no agent-type precedence in this model.
22
- A package source, soul source, deployment/install location, work target, and team
23
- membership are separate facts. Never derive one from another.
24
-
25
- ## Implemented preparation
26
-
27
- Prepare an explicit source export by reference:
28
-
29
- ```bash
30
- oats prepare \
31
- --dir <absolute-deployment> \
32
- --source <git-repository> --revision <selector> \
33
- --export <exported-soul-path> --alias <local-alias> \
34
- [--work directory] --json
35
- ```
36
-
37
- Prepare an alias advertised by an explicit workspace:
38
-
39
- ```bash
40
- oats prepare \
41
- --dir <absolute-deployment> \
42
- --workspace <git-repository> [--workspace-revision <selector>] \
43
- --alias <advertised-alias> [--work directory] --json
44
- ```
45
-
46
- Preparation resolves one source observation, retains the required source and
47
- software trees, resolves provider-owned nonsecret bindings through the same
48
- choice engine, prepares dedicated compatible helpers, and publishes a complete
49
- record before returning a resolution. It does not launch, enroll identities,
50
- create teams, approve executables, or infer a publisher workspace.
51
-
52
- ## Read the result correctly
53
-
54
- - `resolution: null` means no executable captured record was published.
55
- - `needs-configuration` identifies missing bindings/provider inputs; do not fill
56
- them from current config.
57
- - `approval-required` can accompany a complete retained record; approval remains
58
- a separate explicit action.
59
- - `responsibleHuman: null` means messaging is explicitly disabled.
60
- - Helper-authored software, knowledge, team, or resource policy currently
61
- requires dedicated preparation and refuses instead of inheriting the parent.
62
-
63
- ## Not yet a public input
64
-
65
- An explicit standalone context key, onboarding inspection facade, non-directory
66
- work-target placement/setup, and managed launch/runtime capture are still being
67
- integrated. Do not invent flags or derive a standalone key from a path, username,
68
- source alias, or machine identity. A workspace context and standalone context are
69
- mutually exclusive.