nazeyatta 0.2.0a1__tar.gz
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.
- nazeyatta-0.2.0a1/LICENSE +201 -0
- nazeyatta-0.2.0a1/PKG-INFO +356 -0
- nazeyatta-0.2.0a1/README.md +339 -0
- nazeyatta-0.2.0a1/pyproject.toml +32 -0
- nazeyatta-0.2.0a1/setup.cfg +4 -0
- nazeyatta-0.2.0a1/src/nazeyatta/__init__.py +1 -0
- nazeyatta-0.2.0a1/src/nazeyatta/baseline_derivation.py +342 -0
- nazeyatta-0.2.0a1/src/nazeyatta/cli.py +174 -0
- nazeyatta-0.2.0a1/src/nazeyatta/data/generic_rules.yaml +141 -0
- nazeyatta-0.2.0a1/src/nazeyatta/evaluator.py +418 -0
- nazeyatta-0.2.0a1/src/nazeyatta/fresh_handoff.py +132 -0
- nazeyatta-0.2.0a1/src/nazeyatta/ky_gate.py +396 -0
- nazeyatta-0.2.0a1/src/nazeyatta/policy_provenance.py +289 -0
- nazeyatta-0.2.0a1/src/nazeyatta/preflight_runtime_correlation.py +115 -0
- nazeyatta-0.2.0a1/src/nazeyatta/receipt_io.py +51 -0
- nazeyatta-0.2.0a1/src/nazeyatta/reky_gate.py +482 -0
- nazeyatta-0.2.0a1/src/nazeyatta/runtime_fixture_sources.py +212 -0
- nazeyatta-0.2.0a1/src/nazeyatta/runtime_safe_read.py +215 -0
- nazeyatta-0.2.0a1/src/nazeyatta/spec_adoption.py +261 -0
- nazeyatta-0.2.0a1/src/nazeyatta.egg-info/PKG-INFO +356 -0
- nazeyatta-0.2.0a1/src/nazeyatta.egg-info/SOURCES.txt +41 -0
- nazeyatta-0.2.0a1/src/nazeyatta.egg-info/dependency_links.txt +1 -0
- nazeyatta-0.2.0a1/src/nazeyatta.egg-info/entry_points.txt +2 -0
- nazeyatta-0.2.0a1/src/nazeyatta.egg-info/requires.txt +1 -0
- nazeyatta-0.2.0a1/src/nazeyatta.egg-info/top_level.txt +1 -0
- nazeyatta-0.2.0a1/tests/test_baseline_derivation.py +230 -0
- nazeyatta-0.2.0a1/tests/test_baseline_derivation_dogfood.py +128 -0
- nazeyatta-0.2.0a1/tests/test_evaluator.py +145 -0
- nazeyatta-0.2.0a1/tests/test_fixture_source_reky.py +132 -0
- nazeyatta-0.2.0a1/tests/test_fresh_handoff.py +136 -0
- nazeyatta-0.2.0a1/tests/test_input_boundaries.py +135 -0
- nazeyatta-0.2.0a1/tests/test_ky_gate.py +193 -0
- nazeyatta-0.2.0a1/tests/test_policy_hardening.py +147 -0
- nazeyatta-0.2.0a1/tests/test_policy_provenance.py +188 -0
- nazeyatta-0.2.0a1/tests/test_preflight_runtime_correlation.py +183 -0
- nazeyatta-0.2.0a1/tests/test_receipt_io.py +97 -0
- nazeyatta-0.2.0a1/tests/test_reky_gate.py +284 -0
- nazeyatta-0.2.0a1/tests/test_runtime_fixture_sources.py +125 -0
- nazeyatta-0.2.0a1/tests/test_runtime_safe_read.py +143 -0
- nazeyatta-0.2.0a1/tests/test_schema_runtime_parity.py +67 -0
- nazeyatta-0.2.0a1/tests/test_spec_adoption.py +181 -0
- nazeyatta-0.2.0a1/tests/test_task_contract.py +72 -0
- nazeyatta-0.2.0a1/tests/test_worker_ky_contract.py +66 -0
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2026 Catfood Lab
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
|
@@ -0,0 +1,356 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: nazeyatta
|
|
3
|
+
Version: 0.2.0a1
|
|
4
|
+
Summary: Preflight hazard analysis for AI and software workers
|
|
5
|
+
Author: Catfood Lab
|
|
6
|
+
License: Apache-2.0
|
|
7
|
+
Classifier: Development Status :: 3 - Alpha
|
|
8
|
+
Classifier: License :: OSI Approved :: Apache Software License
|
|
9
|
+
Classifier: Programming Language :: Python :: 3
|
|
10
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
11
|
+
Classifier: Topic :: Software Development :: Quality Assurance
|
|
12
|
+
Requires-Python: >=3.11
|
|
13
|
+
Description-Content-Type: text/markdown
|
|
14
|
+
License-File: LICENSE
|
|
15
|
+
Requires-Dist: PyYAML>=6.0
|
|
16
|
+
Dynamic: license-file
|
|
17
|
+
|
|
18
|
+
# NazeYatta
|
|
19
|
+
|
|
20
|
+
[English](README.md) | [日本語](README.ja.md)
|
|
21
|
+
|
|
22
|
+
**NazeYatta is a small command-line preflight checker for AI workers and automation.**
|
|
23
|
+
|
|
24
|
+
It answers one narrow question:
|
|
25
|
+
|
|
26
|
+
> **Before this action happens, are the required checks actually satisfied?**
|
|
27
|
+
|
|
28
|
+
If the answer is not established, NazeYatta does not guess.
|
|
29
|
+
|
|
30
|
+
For example:
|
|
31
|
+
|
|
32
|
+
~~~text
|
|
33
|
+
Proposed action:
|
|
34
|
+
publish this photo
|
|
35
|
+
|
|
36
|
+
Known facts:
|
|
37
|
+
target checked VERIFIED
|
|
38
|
+
worker capability VERIFIED
|
|
39
|
+
publication permission UNKNOWN
|
|
40
|
+
|
|
41
|
+
Rule:
|
|
42
|
+
public publication requires verified permission
|
|
43
|
+
|
|
44
|
+
NazeYatta:
|
|
45
|
+
BLOCK
|
|
46
|
+
~~~
|
|
47
|
+
|
|
48
|
+
NazeYatta does **not** publish the photo.
|
|
49
|
+
NazeYatta does **not** grant permission to publish it.
|
|
50
|
+
|
|
51
|
+
It only performs the preflight check and returns a reproducible result.
|
|
52
|
+
|
|
53
|
+
---
|
|
54
|
+
|
|
55
|
+
## The 30-second mental model
|
|
56
|
+
|
|
57
|
+
~~~text
|
|
58
|
+
Something wants to act
|
|
59
|
+
|
|
|
60
|
+
v
|
|
61
|
+
task snapshot + known facts
|
|
62
|
+
|
|
|
63
|
+
v
|
|
64
|
+
NazeYatta
|
|
65
|
+
checks rules
|
|
66
|
+
|
|
|
67
|
+
v
|
|
68
|
+
PASS / REVIEW / BLOCK
|
|
69
|
+
+ receipt of what was checked
|
|
70
|
+
|
|
|
71
|
+
v
|
|
72
|
+
a separate Human / Worker / Harness
|
|
73
|
+
decides or performs the actual action
|
|
74
|
+
~~~
|
|
75
|
+
|
|
76
|
+
Think of it as a **preflight checklist that a machine can evaluate**.
|
|
77
|
+
|
|
78
|
+
It is useful when you do **not** want:
|
|
79
|
+
|
|
80
|
+
~~~text
|
|
81
|
+
"I could not verify it"
|
|
82
|
+
to become
|
|
83
|
+
"it is probably fine"
|
|
84
|
+
~~~
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
|
|
88
|
+
## Do I need NazeYatta?
|
|
89
|
+
|
|
90
|
+
Maybe not.
|
|
91
|
+
|
|
92
|
+
If one small script with one obvious if-statement solves your problem, use the if-statement.
|
|
93
|
+
|
|
94
|
+
NazeYatta becomes useful when you want several workflows or AI workers to share things such as:
|
|
95
|
+
|
|
96
|
+
- explicit UNKNOWN, MISSING, STALE, and VERIFIED states;
|
|
97
|
+
- reusable preflight rules;
|
|
98
|
+
- consistent CLI exit behavior;
|
|
99
|
+
- a receipt showing what was checked;
|
|
100
|
+
- a hard boundary between **evidence** and **permission to execute**.
|
|
101
|
+
|
|
102
|
+
Examples:
|
|
103
|
+
|
|
104
|
+
- before git push;
|
|
105
|
+
- before deleting or replacing something;
|
|
106
|
+
- before publishing content;
|
|
107
|
+
- before an external write;
|
|
108
|
+
- before using a capability that must be qualified;
|
|
109
|
+
- before acting on a target whose identity must be confirmed.
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
## Run one example
|
|
114
|
+
|
|
115
|
+
Requires Python 3.11+.
|
|
116
|
+
|
|
117
|
+
~~~bash
|
|
118
|
+
git clone https://github.com/hopeless-t/NazeYatta.git
|
|
119
|
+
cd NazeYatta
|
|
120
|
+
python -m venv .venv
|
|
121
|
+
. .venv/bin/activate # Windows: .venv\Scripts\activate
|
|
122
|
+
python -m pip install -e .
|
|
123
|
+
|
|
124
|
+
nazeyatta check examples/publish-photo.yaml
|
|
125
|
+
~~~
|
|
126
|
+
|
|
127
|
+
The example says that publication permission is UNKNOWN.
|
|
128
|
+
|
|
129
|
+
The bundled baseline policy says public publication requires verified permission.
|
|
130
|
+
|
|
131
|
+
So the result is:
|
|
132
|
+
|
|
133
|
+
~~~text
|
|
134
|
+
NAZEYATTA
|
|
135
|
+
👈😽 PRE-FLIGHT KY
|
|
136
|
+
|
|
137
|
+
✋😾 BLOCK
|
|
138
|
+
|
|
139
|
+
NY-PUB-001 External publication requires verified provenance and permission
|
|
140
|
+
hazard: PUBLICATION_WITH_UNKNOWN_RIGHTS
|
|
141
|
+
evidence: publication_permission_verified = UNKNOWN
|
|
142
|
+
effect: BLOCK
|
|
143
|
+
|
|
144
|
+
EXECUTION AUTHORITY: NOT GRANTED BY NAZEYATTA
|
|
145
|
+
~~~
|
|
146
|
+
|
|
147
|
+
Plain language:
|
|
148
|
+
|
|
149
|
+
> **"I cannot confirm that publishing is allowed, so this preflight will not treat it as OK to continue."**
|
|
150
|
+
|
|
151
|
+
Try a simple read-only example too:
|
|
152
|
+
|
|
153
|
+
~~~bash
|
|
154
|
+
nazeyatta check examples/safe-read.yaml
|
|
155
|
+
~~~
|
|
156
|
+
|
|
157
|
+
That example returns PASS.
|
|
158
|
+
|
|
159
|
+
But:
|
|
160
|
+
|
|
161
|
+
~~~text
|
|
162
|
+
PASS != Execution Authority
|
|
163
|
+
~~~
|
|
164
|
+
|
|
165
|
+
A PASS means this preflight found no stronger blocking effect for the supplied snapshot. It does **not** create permission by itself.
|
|
166
|
+
|
|
167
|
+
---
|
|
168
|
+
|
|
169
|
+
## What goes in?
|
|
170
|
+
|
|
171
|
+
For the first run, one small YAML task file is enough.
|
|
172
|
+
|
|
173
|
+
Example:
|
|
174
|
+
|
|
175
|
+
~~~yaml
|
|
176
|
+
task_id: MY-FIRST-READ
|
|
177
|
+
|
|
178
|
+
action:
|
|
179
|
+
operation: read
|
|
180
|
+
side_effect: none
|
|
181
|
+
externality: internal
|
|
182
|
+
|
|
183
|
+
worker:
|
|
184
|
+
required_capability: read_repository
|
|
185
|
+
|
|
186
|
+
semantics:
|
|
187
|
+
critical_meaning_complete: true
|
|
188
|
+
|
|
189
|
+
evidence:
|
|
190
|
+
worker_capability_qualified: VERIFIED
|
|
191
|
+
~~~
|
|
192
|
+
|
|
193
|
+
Save it as my-first-task.yaml, then run:
|
|
194
|
+
|
|
195
|
+
~~~bash
|
|
196
|
+
nazeyatta check my-first-task.yaml
|
|
197
|
+
~~~
|
|
198
|
+
|
|
199
|
+
NazeYatta ships with a small generic baseline policy, so you do not need to design a policy file just to run the first example.
|
|
200
|
+
|
|
201
|
+
At a high level, NazeYatta compares:
|
|
202
|
+
|
|
203
|
+
~~~text
|
|
204
|
+
what you want to do
|
|
205
|
+
+
|
|
206
|
+
what is currently known
|
|
207
|
+
+
|
|
208
|
+
the applicable rules
|
|
209
|
+
~~~
|
|
210
|
+
|
|
211
|
+
and emits a result plus a receipt.
|
|
212
|
+
|
|
213
|
+
---
|
|
214
|
+
|
|
215
|
+
## What comes out?
|
|
216
|
+
|
|
217
|
+
Current outcome types include:
|
|
218
|
+
|
|
219
|
+
- PASS
|
|
220
|
+
- CAUTION
|
|
221
|
+
- REVIEW
|
|
222
|
+
- EVIDENCE_REQUIRED
|
|
223
|
+
- BLOCK
|
|
224
|
+
|
|
225
|
+
Only PASS returns CLI exit status 0.
|
|
226
|
+
|
|
227
|
+
The result can also be emitted as JSON:
|
|
228
|
+
|
|
229
|
+
~~~bash
|
|
230
|
+
nazeyatta check examples/safe-read.yaml --json
|
|
231
|
+
~~~
|
|
232
|
+
|
|
233
|
+
The receipt includes fingerprints and evaluation information so another tool or Human can inspect what was evaluated.
|
|
234
|
+
|
|
235
|
+
---
|
|
236
|
+
|
|
237
|
+
## What NazeYatta is **not**
|
|
238
|
+
|
|
239
|
+
NazeYatta is not:
|
|
240
|
+
|
|
241
|
+
- the AI worker that performs the task;
|
|
242
|
+
- an execution engine;
|
|
243
|
+
- a permission-granting authority;
|
|
244
|
+
- a certification system;
|
|
245
|
+
- a complete policy platform;
|
|
246
|
+
- an autonomous remediation system;
|
|
247
|
+
- proof that the supplied evidence source was truthful or authorized;
|
|
248
|
+
- automatic end-to-end enforcement.
|
|
249
|
+
|
|
250
|
+
The current alpha evaluates supplied task/evidence structure and policy conditions deterministically.
|
|
251
|
+
|
|
252
|
+
For high-impact actions, use a separate enforcement point the worker cannot bypass.
|
|
253
|
+
|
|
254
|
+
---
|
|
255
|
+
|
|
256
|
+
## Why is it called "NazeYatta"?
|
|
257
|
+
|
|
258
|
+
**Naze yatta? / なぜやった?** means roughly:
|
|
259
|
+
|
|
260
|
+
> **"Why did you do that?"**
|
|
261
|
+
|
|
262
|
+
The project started from a recurring AI-worker failure mode:
|
|
263
|
+
|
|
264
|
+
~~~text
|
|
265
|
+
Human:
|
|
266
|
+
"Do not do X."
|
|
267
|
+
|
|
268
|
+
AI worker:
|
|
269
|
+
"Understood. I will not do X."
|
|
270
|
+
|
|
271
|
+
AI worker:
|
|
272
|
+
does X
|
|
273
|
+
~~~
|
|
274
|
+
|
|
275
|
+
NazeYatta moves one part of that problem **before** the action:
|
|
276
|
+
|
|
277
|
+
> What had to be true before acting, and was it actually established?
|
|
278
|
+
|
|
279
|
+
The cat-heavy presentation is intentionally playful. The result semantics are not.
|
|
280
|
+
|
|
281
|
+
---
|
|
282
|
+
|
|
283
|
+
## Where the deeper ideas live
|
|
284
|
+
|
|
285
|
+
You do **not** need to understand these documents to run the first example.
|
|
286
|
+
|
|
287
|
+
Read them when you need the deeper model:
|
|
288
|
+
|
|
289
|
+
- [Semantics](docs/SEMANTICS.md) — Policy != Evidence, Evidence != Authority, states and invariants
|
|
290
|
+
- [Evidence Model](docs/EVIDENCE_MODEL.md) — Evidence Records, provenance linkage, freshness
|
|
291
|
+
- [Policy Model](docs/POLICY_MODEL.md) — applicability and policy effects
|
|
292
|
+
- [Threat Model](docs/THREAT_MODEL.md) — what the project assumes can go wrong
|
|
293
|
+
- [Roadmap](docs/ROADMAP.md) — implemented, research, and deliberately deferred work
|
|
294
|
+
- [Violation Debrief](docs/VIOLATION_DEBRIEF.md) — post-failure debrief structure
|
|
295
|
+
- [Japanese First Steps](docs/FIRST_STEPS.ja.md) — a more procedural Japanese introduction
|
|
296
|
+
|
|
297
|
+
---
|
|
298
|
+
|
|
299
|
+
## Current status
|
|
300
|
+
|
|
301
|
+
NazeYatta is an **alpha research tool**.
|
|
302
|
+
|
|
303
|
+
Implemented preflight foundation:
|
|
304
|
+
|
|
305
|
+
- deterministic YAML preflight evaluation;
|
|
306
|
+
- bundled generic baseline rules;
|
|
307
|
+
- explicit evidence states;
|
|
308
|
+
- conservative CLI exit codes;
|
|
309
|
+
- JSON and human-readable receipts;
|
|
310
|
+
- deterministic task/policy fingerprints;
|
|
311
|
+
- a provenance-linked v0.2 input lane;
|
|
312
|
+
- structured violation-debrief templates;
|
|
313
|
+
- tests and examples.
|
|
314
|
+
|
|
315
|
+
Bounded experimental contracts now also exist for:
|
|
316
|
+
|
|
317
|
+
- typed Worker KY declarations and a deterministic KY validation gate;
|
|
318
|
+
- a single-bounce Fresh Handoff and Boundary Observation / Re-KY comparison;
|
|
319
|
+
- fresh-process, read-only dogfood with local fixture source observation;
|
|
320
|
+
- BaselineDerivationRecord;
|
|
321
|
+
- a bounded dogfood DerivationSpec;
|
|
322
|
+
- a scoped SpecAdoptionRecord.
|
|
323
|
+
|
|
324
|
+
Those contracts and dogfoods demonstrate bounded mechanics. They do **not** turn NazeYatta into a production executor, authority system, IAM/PKI layer, or proof that a rule/spec is normatively correct.
|
|
325
|
+
|
|
326
|
+
Not automatic production end-to-end functionality:
|
|
327
|
+
|
|
328
|
+
- AI-generated Worker KY declarations;
|
|
329
|
+
- production source/runtime adapters and continuous observation;
|
|
330
|
+
- live execution enforcement;
|
|
331
|
+
- authority authentication for evidence, policy, or derivation-spec adoption;
|
|
332
|
+
- normative/semantic correctness proof;
|
|
333
|
+
- automatic remediation;
|
|
334
|
+
- authority generation.
|
|
335
|
+
|
|
336
|
+
~~~text
|
|
337
|
+
Fixture Dogfood != Production Runtime
|
|
338
|
+
RECORD_BOUND != Authority Authenticated
|
|
339
|
+
PROVENANCE_BOUND != Semantic Correctness Verified
|
|
340
|
+
Unknown != Safe
|
|
341
|
+
Worker Self-Declaration != Evidence
|
|
342
|
+
Evidence != Authority
|
|
343
|
+
PASS != Execution Authority
|
|
344
|
+
~~~
|
|
345
|
+
|
|
346
|
+
## Contributing
|
|
347
|
+
|
|
348
|
+
See [CONTRIBUTING.md](CONTRIBUTING.md).
|
|
349
|
+
|
|
350
|
+
If the repository is hard to understand, that is useful bug evidence. Please open an issue and describe where your mental model broke — even if the answer is simply:
|
|
351
|
+
|
|
352
|
+
> **"I do not know what I am looking at."**
|
|
353
|
+
|
|
354
|
+
## License
|
|
355
|
+
|
|
356
|
+
Apache-2.0. See [LICENSE](LICENSE).
|