@hap-labs/human-agent-paradigm 0.1.0 → 0.2.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/README.md +19 -45
- package/assets/EN/CONFORMANCE_CHECKLIST.md +156 -161
- package/assets/EN/CONTRACT_TEMPLATE.md +108 -112
- package/assets/EN/DECISION_REQUEST_TEMPLATE.md +76 -81
- package/assets/EN/DELIVERY_REPORT_TEMPLATE.md +103 -83
- package/assets/EN/DERIVED_SPECIFICATION.md +73 -76
- package/assets/EN/HUMAN_AGENT_PARADIGM.md +26 -30
- package/docs/ZH_CN/README.md +30 -0
- package/package.json +7 -16
- package/CHANGELOG.md +0 -21
- package/README.zh-CN.md +0 -52
- package/scripts/python/repo_governance_check/__init__.py +0 -3
- package/scripts/python/repo_governance_check/__main__.py +0 -6
- package/scripts/python/repo_governance_check/checks.py +0 -359
- package/scripts/python/repo_governance_check/cli.py +0 -115
- package/scripts/python/repo_governance_check/config.py +0 -33
- package/scripts/python/repo_governance_check/governance_check_config.json +0 -166
- package/scripts/python/repo_governance_check/report.py +0 -79
|
@@ -1,43 +1,38 @@
|
|
|
1
1
|
# Contract Template (execution layer)
|
|
2
2
|
|
|
3
|
-
> English translation of the frozen document `CONTRACT_TEMPLATE.md`. The Simplified Chinese original is authoritative
|
|
4
|
-
> for governance and is the signing copy; this English copy is provided for agent reading, understanding, and reference.
|
|
5
|
-
> Version markers mirror the original (v1.0). Upstream references point to `HUMAN_AGENT_PARADIGM.md` and
|
|
6
|
-
> `DERIVED_SPECIFICATION.md`.
|
|
7
|
-
|
|
8
3
|
Version: v1.0
|
|
9
4
|
Hierarchy: constitution `HUMAN_AGENT_PARADIGM.md` v1.0 → derived specification `DERIVED_SPECIFICATION.md` v1.0 → this
|
|
10
5
|
template
|
|
11
|
-
Status: execution-layer template · produced
|
|
6
|
+
Status: execution-layer template · produced under the Owner's authorization
|
|
12
7
|
Applicable scope: the P3 contract-establishment phase; the first basis of judgment for all subsequent work (provided it
|
|
13
8
|
does not conflict with the constitution or the derived specification)
|
|
14
9
|
|
|
15
|
-
## Usage
|
|
10
|
+
## Usage rules
|
|
16
11
|
|
|
17
12
|
1. This template is filled in by the Agent at P3 and confirmed and signed by the human (the Owner); design and
|
|
18
|
-
implementation
|
|
19
|
-
2. None of C1–C10 may be omitted; small tasks may shorten
|
|
20
|
-
is the criterion, what is the evidence".
|
|
13
|
+
implementation may not begin before the contract is established.
|
|
14
|
+
2. None of C1–C10 may be omitted; small tasks may shorten each section, but must answer item by item "is it defined,
|
|
15
|
+
what is the criterion, what is the evidence".
|
|
21
16
|
3. All thresholds, criteria, and budgets are proposed by the Agent and confirmed by the human; the Agent may not
|
|
22
17
|
unilaterally relax them, and later changes must go through C10.
|
|
23
|
-
4. The contract ID is unique and versions
|
|
18
|
+
4. The contract ID is unique and versions traceable; every change must record the reason, affected clauses, and the
|
|
24
19
|
human's approval.
|
|
25
|
-
5. This contract must not conflict with the constitution or the derived specification; on conflict
|
|
26
|
-
|
|
20
|
+
5. This contract must not conflict with the constitution or the derived specification; on conflict the higher
|
|
21
|
+
specification prevails and the matter returns to the contract process.
|
|
27
22
|
|
|
28
23
|
---
|
|
29
24
|
|
|
30
|
-
## Contract
|
|
25
|
+
## Contract metadata
|
|
31
26
|
|
|
32
|
-
| Field | Content
|
|
33
|
-
|
|
34
|
-
| Contract ID |
|
|
35
|
-
| Version |
|
|
36
|
-
| Product/task name |
|
|
37
|
-
| Upstream intent record |
|
|
38
|
-
| Direction-decision record |
|
|
39
|
-
| Constitutional traceability | constitution 5.2 P3, 3.2, 7.3; derived
|
|
40
|
-
| Status | `Draft` / `Signed` / `
|
|
27
|
+
| Field | Content |
|
|
28
|
+
|:----------------------------|:-------------------------------------------------------------|
|
|
29
|
+
| Contract ID | |
|
|
30
|
+
| Version | |
|
|
31
|
+
| Product/task name | |
|
|
32
|
+
| Upstream intent record | |
|
|
33
|
+
| Direction-decision record | |
|
|
34
|
+
| Constitutional traceability | constitution 5.2 P3, 3.2, 7.3; derived specification 2.1–2.4 |
|
|
35
|
+
| Status | `Draft` / `Signed` / `Changed` / `Terminated` |
|
|
41
36
|
|
|
42
37
|
---
|
|
43
38
|
|
|
@@ -45,45 +40,45 @@ does not conflict with the constitution or the derived specification)
|
|
|
45
40
|
|
|
46
41
|
**Original intent (stated by the human):**
|
|
47
42
|
|
|
48
|
-
**Agent restatement (
|
|
43
|
+
**Agent restatement (must be confirmed by the human):**
|
|
49
44
|
|
|
50
|
-
**"What matters more"
|
|
45
|
+
**"What matters more" ranking:** 1. ______ 2. ______ 3. ______
|
|
51
46
|
|
|
52
47
|
**Key preferences and values:**
|
|
53
48
|
|
|
54
|
-
**Differences
|
|
49
|
+
**Differences to confirm (if any):**
|
|
55
50
|
|
|
56
|
-
- [ ] The human has confirmed the restatement and
|
|
51
|
+
- [ ] The human has confirmed the above restatement and ranking.
|
|
57
52
|
|
|
58
53
|
---
|
|
59
54
|
|
|
60
55
|
## C2 Scope and Non-Goals
|
|
61
56
|
|
|
62
|
-
| No. | In-scope
|
|
63
|
-
|
|
64
|
-
| S1 |
|
|
65
|
-
| S2 |
|
|
57
|
+
| No. | In-scope deliverables | Judgeable completion criteria (refer to C4/C5 criterion IDs) |
|
|
58
|
+
|:----|:----------------------|:-------------------------------------------------------------|
|
|
59
|
+
| S1 | | |
|
|
60
|
+
| S2 | | |
|
|
66
61
|
|
|
67
|
-
**Explicit non-goals (not delivered this
|
|
62
|
+
**Explicit non-goals (not delivered this time):**
|
|
68
63
|
|
|
69
|
-
**Product form:** (what
|
|
64
|
+
**Product form:** (what deliverable, runnable, usable outcome is; not limited to software)
|
|
70
65
|
|
|
71
66
|
---
|
|
72
67
|
|
|
73
68
|
## C3 Constraints and Bottom Lines
|
|
74
69
|
|
|
75
|
-
| Category | Constraint | Non-
|
|
76
|
-
|
|
77
|
-
| Time |
|
|
78
|
-
| Cost |
|
|
79
|
-
| Risk |
|
|
80
|
-
| Safety |
|
|
81
|
-
| Compliance |
|
|
82
|
-
| Privacy/confidentiality |
|
|
83
|
-
| Technology/resources |
|
|
70
|
+
| Category | Constraint content | Non-negotiable criterion | Handling on conflict |
|
|
71
|
+
|:------------------------|:-------------------|:-------------------------|:---------------------|
|
|
72
|
+
| Time | | | |
|
|
73
|
+
| Cost | | | |
|
|
74
|
+
| Risk | | | |
|
|
75
|
+
| Safety | | | |
|
|
76
|
+
| Compliance | | | |
|
|
77
|
+
| Privacy/confidentiality | | | |
|
|
78
|
+
| Technology/resources | | | |
|
|
84
79
|
|
|
85
|
-
**Bottom-line statement:** safety and compliance
|
|
86
|
-
|
|
80
|
+
**Bottom-line statement:** safety and compliance are above all efficiency and need metrics; human authorization does not
|
|
81
|
+
override law or the basic safety bottom line.
|
|
87
82
|
|
|
88
83
|
---
|
|
89
84
|
|
|
@@ -91,33 +86,33 @@ overrides law or basic safety bottom lines.
|
|
|
91
86
|
|
|
92
87
|
**Definition of done (DoD):** a "completed" claim is allowed only when all of the following hold:
|
|
93
88
|
|
|
94
|
-
1.
|
|
95
|
-
2.
|
|
96
|
-
3.
|
|
97
|
-
4.
|
|
89
|
+
1. The corresponding C2 deliverable is runnable/usable;
|
|
90
|
+
2. Every completion claim is attached to real evidence (evidence ID pointing into the evidence package);
|
|
91
|
+
3. C6 multi-view review passed, with no unresolved defect inside the contract scope;
|
|
92
|
+
4. Failures and incomplete items are listed truthfully.
|
|
98
93
|
|
|
99
|
-
**Claim–evidence mapping (
|
|
94
|
+
**Claim–evidence mapping (made concrete for this project):**
|
|
100
95
|
|
|
101
|
-
| Claim type |
|
|
96
|
+
| Claim type | Evidence form required | Evidence destination |
|
|
102
97
|
|:-----------------------------|:-------------------------------------------------------------------------|:---------------------|
|
|
103
98
|
| Feature/deliverable complete | runnable/usable artifact + run/use/test records | evidence package |
|
|
104
99
|
| Quality met | review/test results + defect records + fix/re-verification records | evidence package |
|
|
105
|
-
| State report | snapshot of current real state + differences from previous state
|
|
100
|
+
| State report | snapshot of current real state + differences from the previous state | evidence package |
|
|
106
101
|
| Performance met | measurement plan under contract conditions + results + environment notes | evidence package |
|
|
107
|
-
| Asset reused | source + verification
|
|
102
|
+
| Asset reused | source + verification record + post-reuse results | evidence package |
|
|
108
103
|
|
|
109
|
-
**State-sync method:** (when to sync, what to sync, in which objective metrics)
|
|
104
|
+
**State-sync method:** (when to sync, what to sync, expressed in which objective metrics)
|
|
110
105
|
|
|
111
|
-
**Failure-reporting method:** (how
|
|
106
|
+
**Failure-reporting method:** (how to report, what content and time limits when a failure/unmet standard is found; vague
|
|
112
107
|
wording forbidden)
|
|
113
108
|
|
|
114
109
|
**Prohibited behaviors:** reporting things that did not happen or were not completed; substituting simulation,
|
|
115
|
-
description, or imagination for real output; fabricating evidence or citing
|
|
116
|
-
evidence with self-assessment.
|
|
110
|
+
description, or imagination for real output; fabricating evidence or citing things that do not exist; replacing
|
|
111
|
+
checkable evidence with self-assessment.
|
|
117
112
|
|
|
118
113
|
---
|
|
119
114
|
|
|
120
|
-
## C5 Excellence Criteria (five dimensions,
|
|
115
|
+
## C5 Excellence Criteria (five dimensions, judgeable item by item)
|
|
121
116
|
|
|
122
117
|
**Filling rule:** every criterion must be writable as "object + condition + observable result + threshold/criterion +
|
|
123
118
|
evidence source"; adjectives alone are not allowed.
|
|
@@ -130,40 +125,41 @@ evidence source"; adjectives alone are not allowed.
|
|
|
130
125
|
| E6.4.x | Perfect experience | | | | |
|
|
131
126
|
| E6.5.x | Excellent performance | | | | |
|
|
132
127
|
|
|
133
|
-
- [ ] All five dimension criteria are defined; no "adjective as acceptance"
|
|
134
|
-
- [ ] The human confirmed all thresholds; the Agent
|
|
128
|
+
- [ ] All five dimension criteria are defined; no blank "adjective as acceptance" cell.
|
|
129
|
+
- [ ] The human has confirmed all thresholds; the Agent has not unilaterally relaxed them.
|
|
135
130
|
|
|
136
131
|
---
|
|
137
132
|
|
|
138
133
|
## C6 Multi-View Review Requirements
|
|
139
134
|
|
|
140
|
-
| Perspective | Problems that must be sought
|
|
141
|
-
|
|
142
|
-
| Product | intent drift, scope
|
|
143
|
-
| User | whether target users complete independently,
|
|
144
|
-
| Engineering | design soundness, implementation craft, maintainability, quality debt, boundaries
|
|
145
|
-
| Adversarial | assume completion claims false; find counterexamples, exceptional paths, safety/compliance holes | same
|
|
135
|
+
| Perspective | Problems that must be sought | Review-record requirements |
|
|
136
|
+
|:------------|:-----------------------------------------------------------------------------------------------------|:--------------------------------------------------------------------|
|
|
137
|
+
| Product | intent drift, scope omission, non-goal bloat, value proposition not holding | independent standpoint, defect-finding method, findings, conclusion |
|
|
138
|
+
| User | whether target users can complete independently, path, feedback, error recovery, friction | same as above |
|
|
139
|
+
| Engineering | design soundness, implementation craft, maintainability, quality debt, boundaries | same as above |
|
|
140
|
+
| Adversarial | assume completion claims are false; find counterexamples, exceptional paths, safety/compliance holes | same as above |
|
|
146
141
|
|
|
147
|
-
**Independence:** review standpoint, method, and records are independent of the production process of the content
|
|
148
|
-
review; the same entity
|
|
142
|
+
**Independence:** the review standpoint, method, and records are independent of the production process of the content
|
|
143
|
+
under review; when the same entity performs the review, it must explicitly switch standpoint and use independent
|
|
144
|
+
methods.
|
|
149
145
|
|
|
150
146
|
**Defect closure:** Blockers/Majors must be fixed and re-verified; Minors should be fixed; any defect chosen not to fix
|
|
151
|
-
must reopen the contract, be
|
|
147
|
+
must reopen the contract, be approved by the human as moved out of scope, and be explicitly disclosed.
|
|
152
148
|
|
|
153
|
-
**Exit criteria:** all C5 criteria met
|
|
149
|
+
**Exit criteria:** all C5 criteria met, with no known unresolved defect inside the contract scope.
|
|
154
150
|
|
|
155
151
|
---
|
|
156
152
|
|
|
157
153
|
## C7 Autonomy Budget
|
|
158
154
|
|
|
159
|
-
| Item | Content
|
|
160
|
-
|
|
161
|
-
| Authorized scope |
|
|
162
|
-
| Risk threshold | escalate
|
|
163
|
-
| Cost cap | escalate
|
|
164
|
-
| Self-decidable matters |
|
|
165
|
-
| Must-escalate matters |
|
|
166
|
-
| Boundary-touch action |
|
|
155
|
+
| Item | Content |
|
|
156
|
+
|:-----------------------|:---------------------|
|
|
157
|
+
| Authorized scope | |
|
|
158
|
+
| Risk threshold | escalate if exceeded |
|
|
159
|
+
| Cost cap | escalate if exceeded |
|
|
160
|
+
| Self-decidable matters | |
|
|
161
|
+
| Must-escalate matters | |
|
|
162
|
+
| Boundary-touch action | |
|
|
167
163
|
|
|
168
164
|
**Rules:** no asking inside the boundaries; escalate immediately on touching a boundary; the autonomy budget may only be
|
|
169
165
|
adjusted by the human in a contract or explicit authorization; in-budget self-decisions must not conflict with the
|
|
@@ -186,56 +182,56 @@ contract or effectively lower the reliability or excellence standard.
|
|
|
186
182
|
|
|
187
183
|
**Sole acceptance basis:** this contract (C2–C5, C6, C8).
|
|
188
184
|
|
|
189
|
-
**Acceptance
|
|
190
|
-
|
|
191
|
-
|
|
185
|
+
**Acceptance action:** the human verifies evidence item by item against the contract and signs the acceptance conclusion
|
|
186
|
+
with a time; the Agent must not replace contract requirements with self-justification, self-assessment, or "looks
|
|
187
|
+
compliant".
|
|
192
188
|
|
|
193
|
-
**
|
|
189
|
+
**Prohibited:** adding out-of-contract requirements at acceptance time; new requirements must return to P0/P3 to be
|
|
194
190
|
re-aligned and re-priced.
|
|
195
191
|
|
|
196
192
|
---
|
|
197
193
|
|
|
198
194
|
## C10 Change, Termination, and Failure Handling
|
|
199
195
|
|
|
200
|
-
|
|
|
201
|
-
|
|
202
|
-
|
|
|
203
|
-
| Facts conflict with the contract
|
|
204
|
-
|
|
|
205
|
-
| Deviation from a confirmed direction
|
|
206
|
-
| Reliability and excellence cannot both be met within constraints
|
|
207
|
-
|
|
|
208
|
-
| Acceptance fails
|
|
196
|
+
| Triggering situation | Handling |
|
|
197
|
+
|:---------------------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------|
|
|
198
|
+
| The human changes intent/constraints | return to P0/P3; affected parts re-priced |
|
|
199
|
+
| Facts conflict with the contract | stop, report truthfully, submit redirect/reopen proposal |
|
|
200
|
+
| New situation the contract does not cover and that affects direction | return to P3 to amend the contract |
|
|
201
|
+
| Deviation from a confirmed direction | must be proposed and approved first; acting first and telling later, or acting and staying silent, forbidden |
|
|
202
|
+
| Reliability and excellence cannot both be met within constraints | stop, escalate the trade-off, request constraint adjustment; no silent trade-off |
|
|
203
|
+
| The human stops the project | deliver what was actually completed, evidence, and an incomplete-state statement; nothing incomplete may be claimed complete |
|
|
204
|
+
| Acceptance fails | fix per the contract defect list, or reopen the contract to adjust criteria |
|
|
209
205
|
|
|
210
206
|
---
|
|
211
207
|
|
|
212
|
-
## Traceability and
|
|
208
|
+
## Traceability and Effect
|
|
213
209
|
|
|
214
|
-
| Contract section | Constitutional clauses served | Derived
|
|
215
|
-
|
|
216
|
-
| C1 | 1.2 S3, 4.1, 5.2 P0 | 3.1
|
|
217
|
-
| C2 | 1.4, 5.2 P3 | 2.1
|
|
218
|
-
| C3 | 3.4, 7.3, 7.4 | 2.1, 7.3
|
|
219
|
-
| C4 | 3.1, 5.5 | 2.1, 5
|
|
220
|
-
| C5 | 3.2, 6.1–6.6 | 2.2, 2.3, 6
|
|
221
|
-
| C6 | 3.2, 6.6 | 6.2–6.5
|
|
222
|
-
| C7 | 7.3, A4 | 7.3
|
|
223
|
-
| C8 | 1.3, 5.5 | 1.1
|
|
224
|
-
| C9 | 5.5 | 3.8
|
|
225
|
-
| C10 | 5.3, 5.4, 1.4 | 2.4, 3.11
|
|
210
|
+
| Contract section | Constitutional clauses served | Derived specification served |
|
|
211
|
+
|:-----------------|:------------------------------|:-----------------------------|
|
|
212
|
+
| C1 | 1.2 S3, 4.1, 5.2 P0 | 3.1 |
|
|
213
|
+
| C2 | 1.4, 5.2 P3 | 2.1 |
|
|
214
|
+
| C3 | 3.4, 7.3, 7.4 | 2.1, 7.3 |
|
|
215
|
+
| C4 | 3.1, 5.5 | 2.1, 5 |
|
|
216
|
+
| C5 | 3.2, 6.1–6.6 | 2.2, 2.3, 6 |
|
|
217
|
+
| C6 | 3.2, 6.6 | 6.2–6.5 |
|
|
218
|
+
| C7 | 7.3, A4 | 7.3 |
|
|
219
|
+
| C8 | 1.3, 5.5 | 1.1 |
|
|
220
|
+
| C9 | 5.5 | 3.8 |
|
|
221
|
+
| C10 | 5.3, 5.4, 1.4 | 2.4, 3.11 |
|
|
226
222
|
|
|
227
|
-
**Pre-delivery gate:**
|
|
228
|
-
|
|
223
|
+
**Pre-delivery gate:** run the Conformance Self-Check Checklist v1.0 groups A–I; all ★ items pass; if "the paradigm has
|
|
224
|
+
been implemented" is claimed, J1–J7 must also all pass.
|
|
229
225
|
|
|
230
226
|
---
|
|
231
227
|
|
|
232
228
|
## Signature and Revision
|
|
233
229
|
|
|
234
|
-
| Role
|
|
235
|
-
|
|
236
|
-
| Agent
|
|
237
|
-
| Human (Owner)
|
|
230
|
+
| Role | Content | Signature | Time |
|
|
231
|
+
|:------------------------|:-------------------------------------------------------------------------|:----------|:-----|
|
|
232
|
+
| Agent drafted | complete, unbiased disclosure of pros, cons, cost, and standard strength | | |
|
|
233
|
+
| Human (Owner) confirmed | confirm intent, constraints, criteria, and budget | | |
|
|
238
234
|
|
|
239
|
-
| Version | Date | Change | Affected clauses | Human approval |
|
|
240
|
-
|
|
241
|
-
| | |
|
|
235
|
+
| Version | Date | Change content | Affected clauses | Human approval |
|
|
236
|
+
|:--------|:-----|:---------------|:-----------------|:---------------|
|
|
237
|
+
| | | | | |
|
|
@@ -1,26 +1,21 @@
|
|
|
1
1
|
# Decision Request and Necessary Information Request Template (execution layer)
|
|
2
2
|
|
|
3
|
-
> English translation of the frozen document `DECISION_REQUEST_TEMPLATE.md`. The Simplified Chinese original is
|
|
4
|
-
> authoritative for governance; this English copy is provided for agent reading, understanding, and reference. Version
|
|
5
|
-
> markers mirror the original (v1.0). Upstream references point to `HUMAN_AGENT_PARADIGM.md` and
|
|
6
|
-
> `DERIVED_SPECIFICATION.md`.
|
|
7
|
-
|
|
8
3
|
Version: v1.0
|
|
9
4
|
Hierarchy: constitution `HUMAN_AGENT_PARADIGM.md` v1.0 → derived specification `DERIVED_SPECIFICATION.md` v1.0 → this
|
|
10
5
|
template
|
|
11
|
-
Status: execution-layer template · produced
|
|
12
|
-
Applicable scope: any interaction
|
|
13
|
-
(preference/value, authorization/responsibility)
|
|
6
|
+
Status: execution-layer template · produced under the Owner's authorization
|
|
7
|
+
Applicable scope: any interaction in P0–P7 that requires a human response; Part A is for necessary decisions
|
|
8
|
+
(preference/value, authorization/responsibility), Part B for necessary information completion in P0/P1
|
|
14
9
|
|
|
15
|
-
## Usage
|
|
10
|
+
## Usage rules
|
|
16
11
|
|
|
17
|
-
1. Run the necessity test first: anything the Agent
|
|
12
|
+
1. Run the necessity test first: anything the Agent can ascertain, verify, or cover under existing authorization must
|
|
18
13
|
not be sent to the human.
|
|
19
14
|
2. "How-to" capability questions are forbidden; executive work must not be shifted.
|
|
20
|
-
3. Part A decision
|
|
15
|
+
3. A Part A decision request must carry all six elements (background summary, substantive options, recommendation,
|
|
21
16
|
reason, default choice, decision impact) and state a response window.
|
|
22
|
-
4. Preference/value
|
|
23
|
-
authorization/responsibility
|
|
17
|
+
4. Preference/value type: when the human does not respond before the deadline, proceed on the default and disclose it;
|
|
18
|
+
authorization/responsibility type: no default, must wait for an explicit decision.
|
|
24
19
|
5. Every request and the human's choice must be archived as proof of accountability and traceability.
|
|
25
20
|
|
|
26
21
|
---
|
|
@@ -29,25 +24,25 @@ Applicable scope: any interaction during P0–P7 that needs a human response; Pa
|
|
|
29
24
|
|
|
30
25
|
### A0 Metadata
|
|
31
26
|
|
|
32
|
-
| Field | Content
|
|
33
|
-
|
|
34
|
-
| Request ID |
|
|
35
|
-
| Contract ID |
|
|
36
|
-
| Current phase |
|
|
37
|
-
| Request type | `P preference/value` / `A authorization/responsibility`
|
|
38
|
-
| Risk level | `High/Medium/Low` (
|
|
39
|
-
| Created at |
|
|
27
|
+
| Field | Content |
|
|
28
|
+
|:--------------|:----------------------------------------------------------------|
|
|
29
|
+
| Request ID | |
|
|
30
|
+
| Contract ID | |
|
|
31
|
+
| Current phase | |
|
|
32
|
+
| Request type | `P preference/value` / `A authorization/responsibility` |
|
|
33
|
+
| Risk level | `High/Medium/Low` (determines the window and escalation method) |
|
|
34
|
+
| Created at | |
|
|
40
35
|
|
|
41
|
-
### A1 Necessity Test (
|
|
36
|
+
### A1 Necessity Test (required; must not be sent if it fails)
|
|
42
37
|
|
|
43
|
-
1. Can
|
|
38
|
+
1. Can this matter be resolved by the Agent through information gathering, reasoning, verification, or existing
|
|
44
39
|
authorization?
|
|
45
|
-
- `Yes` → **
|
|
40
|
+
- `Yes` → **Stop sending; the Agent decides.**
|
|
46
41
|
- `No` → continue to step 2.
|
|
47
|
-
2. Is
|
|
48
|
-
|
|
49
|
-
3. If borderline: wrong self-decision costly and irreversible → escalate; cheap and reversible → decide and
|
|
50
|
-
afterwards.
|
|
42
|
+
2. Is this matter essentially the human's preference/value, or authorization/responsibility? (choose only one, and state
|
|
43
|
+
the basis)
|
|
44
|
+
3. If borderline: a wrong self-decision that is costly and irreversible → escalate; cheap and reversible → decide and
|
|
45
|
+
disclose afterwards.
|
|
51
46
|
4. Why this request cannot be self-decided by the Agent:
|
|
52
47
|
|
|
53
48
|
### A2 Background Summary
|
|
@@ -55,38 +50,38 @@ Applicable scope: any interaction during P0–P7 that needs a human response; Pa
|
|
|
55
50
|
**Enough for an independent third party to understand the facts needed for the decision, without irrelevant
|
|
56
51
|
information:**
|
|
57
52
|
|
|
58
|
-
**Contract clauses directly
|
|
53
|
+
**Contract clauses directly relevant to this decision:**
|
|
59
54
|
|
|
60
55
|
### A3 Substantive Options
|
|
61
56
|
|
|
62
|
-
**At least two for type
|
|
57
|
+
**At least two for P-type; at least "approve/not approve" for A-type. For each option state the key difference, benefit,
|
|
63
58
|
cost, and risk.**
|
|
64
59
|
|
|
65
|
-
| Option | Content | Key difference | Benefit | Cost/risk |
|
|
60
|
+
| Option | Content | Key difference | Benefit | Cost/risk | Effect on standard strength |
|
|
66
61
|
|:---------|:--------|:---------------|:--------|:----------|:----------------------------|
|
|
67
62
|
| Option 1 | | | | | |
|
|
68
63
|
| Option 2 | | | | | |
|
|
69
64
|
| (if any) | | | | | |
|
|
70
65
|
|
|
71
|
-
**Substantive-difference check:** the options differ discernibly on key dimensions such as scope/path/quality
|
|
72
|
-
strategy/cost-risk/experience orientation — not rewording.
|
|
66
|
+
**Substantive-difference check:** the above options differ discernibly on key dimensions such as scope/path/quality
|
|
67
|
+
strategy/cost-risk/experience orientation — not mere rewording.
|
|
73
68
|
|
|
74
|
-
### A4 Recommendation and
|
|
69
|
+
### A4 Recommendation and Reason
|
|
75
70
|
|
|
76
71
|
| Field | Content |
|
|
77
72
|
|:---------------------------------------|:--------|
|
|
78
73
|
| Recommended option | |
|
|
79
|
-
|
|
|
74
|
+
| Reason for recommendation | |
|
|
80
75
|
| Cost of the recommendation | |
|
|
81
76
|
| Impact of rejecting the recommendation | |
|
|
82
77
|
|
|
83
|
-
### A5 Default Choice and
|
|
78
|
+
### A5 Default Choice and Overdue Handling
|
|
84
79
|
|
|
85
|
-
| Field
|
|
86
|
-
|
|
87
|
-
| Default option
|
|
88
|
-
|
|
|
89
|
-
|
|
|
80
|
+
| Field | Content |
|
|
81
|
+
|:-------------------------------------|:------------------------------------------------------------------------------------------|
|
|
82
|
+
| Default option | fillable for P-type; A-type must read "no default, wait for an explicit decision" |
|
|
83
|
+
| When the default takes effect | only for preference/value type when the human does not respond within the response window |
|
|
84
|
+
| How default advancement is disclosed | traced in the decision record and the delivery report |
|
|
90
85
|
|
|
91
86
|
### A6 Decision Impact
|
|
92
87
|
|
|
@@ -97,61 +92,61 @@ strategy/cost-risk/experience orientation — not rewording.
|
|
|
97
92
|
|
|
98
93
|
### A7 Response Window
|
|
99
94
|
|
|
100
|
-
| Field | Content
|
|
101
|
-
|
|
102
|
-
| Suggested response window |
|
|
103
|
-
|
|
|
104
|
-
|
|
|
95
|
+
| Field | Content |
|
|
96
|
+
|:--------------------------|:---------------------------------------------------------------------------------|
|
|
97
|
+
| Suggested response window | |
|
|
98
|
+
| Basis for the window | risk, cost, time sensitivity |
|
|
99
|
+
| Overdue handling | P-type: proceed on the A5 default and trace it; A-type: keep waiting, no default |
|
|
105
100
|
|
|
106
101
|
### A8 The Human's Decision and Trace
|
|
107
102
|
|
|
108
|
-
| Field | Content
|
|
109
|
-
|
|
110
|
-
|
|
|
111
|
-
| Basis
|
|
112
|
-
| Decision-impact confirmation |
|
|
113
|
-
| Decision time |
|
|
114
|
-
| Traceability references | constitution 4.3/4.4; derived
|
|
103
|
+
| Field | Content |
|
|
104
|
+
|:-----------------------------|:----------------------------------------------------------------------|
|
|
105
|
+
| The human's choice | |
|
|
106
|
+
| Basis for the choice | |
|
|
107
|
+
| Decision-impact confirmation | |
|
|
108
|
+
| Decision time | |
|
|
109
|
+
| Traceability references | constitution 4.3/4.4; derived specification 4.1–4.4; contract clauses |
|
|
115
110
|
|
|
116
111
|
---
|
|
117
112
|
|
|
118
113
|
## Part B Necessary Information Request (P0/P1 only)
|
|
119
114
|
|
|
120
|
-
### B0 Pre-
|
|
115
|
+
### B0 Pre-check (must not be sent if it fails)
|
|
121
116
|
|
|
122
|
-
- [ ] This request
|
|
123
|
-
- [ ] Self-service
|
|
124
|
-
- [ ]
|
|
117
|
+
- [ ] This request occurs in P0/P1.
|
|
118
|
+
- [ ] Self-service has been tried, with at least one channel tried recorded.
|
|
119
|
+
- [ ] This information is necessary to continue and cannot be replaced by reasoning, verification, or existing
|
|
125
120
|
authorization.
|
|
126
|
-
- [ ] Contains no "how-to" and
|
|
121
|
+
- [ ] Contains no "how-to" and does not require the human to do executive work.
|
|
127
122
|
|
|
128
123
|
### B1 Request Content
|
|
129
124
|
|
|
130
|
-
| Field
|
|
131
|
-
|
|
132
|
-
| Request ID
|
|
133
|
-
| Contract/intent record
|
|
134
|
-
| Exact missing information
|
|
135
|
-
| Which
|
|
136
|
-
| Self-service channels already tried
|
|
137
|
-
| Why it cannot be obtained independently
|
|
138
|
-
| How the Agent will degrade if it cannot be provided
|
|
139
|
-
|
|
140
|
-
### B2 The Human's
|
|
141
|
-
|
|
142
|
-
| Field
|
|
143
|
-
|
|
144
|
-
| Information
|
|
145
|
-
| Record the information enters
|
|
146
|
-
|
|
|
147
|
-
| Traceability references
|
|
125
|
+
| Field | Content |
|
|
126
|
+
|:------------------------------------------------------------|:--------|
|
|
127
|
+
| Request ID | |
|
|
128
|
+
| Contract/intent record | |
|
|
129
|
+
| Exact missing information | |
|
|
130
|
+
| Which fact judgment/contract clause this information is for | |
|
|
131
|
+
| Self-service channels already tried | |
|
|
132
|
+
| Why it cannot be obtained independently | |
|
|
133
|
+
| How the Agent will degrade if it cannot be provided | |
|
|
134
|
+
|
|
135
|
+
### B2 The Human's Reply and Trace
|
|
136
|
+
|
|
137
|
+
| Field | Content |
|
|
138
|
+
|:-------------------------------|:---------------------------------------------------------|
|
|
139
|
+
| Information the human provided | |
|
|
140
|
+
| Record the information enters | intent record / fact-and-constraint baseline |
|
|
141
|
+
| Reply time | |
|
|
142
|
+
| Traceability references | constitution 4.2, 5.2 P1; derived specification 4.1, 4.4 |
|
|
148
143
|
|
|
149
144
|
---
|
|
150
145
|
|
|
151
|
-
## Pre-
|
|
146
|
+
## Pre-send Self-Check
|
|
152
147
|
|
|
153
148
|
- [ ] Not a "how-to" question.
|
|
154
|
-
- [ ] Not
|
|
155
|
-
- [ ] Part A has all six elements; type
|
|
156
|
-
- [ ] Response window and
|
|
157
|
-
- [ ] Disclosure complete and unbiased;
|
|
149
|
+
- [ ] Not a matter the Agent can decide itself.
|
|
150
|
+
- [ ] Part A has all six elements; P-type has ≥2 substantively different options; A-type has no default.
|
|
151
|
+
- [ ] Response window and overdue handling are stated.
|
|
152
|
+
- [ ] Disclosure is complete and unbiased; information advantage does not induce weaker standards.
|