-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathyaml
More file actions
261 lines (222 loc) · 8.14 KB
/
yaml
File metadata and controls
261 lines (222 loc) · 8.14 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
structural_authorship_protocol:
version: "0.1"
protocol_id: "sap:structural-authorship-protocol:v0.1"
title: "Structural Authorship Protocol"
short_name: "SAP"
concept_en: "Structural Authorship"
concept_jp: "構造著作権"
status: "draft"
layer: "normative_protocol"
description: >
A protocol-oriented framework for recognizing, preserving, and tracing
meaning-generating structures in the age of AI, including origin,
lineage, modification history, and value reflux.
purpose:
- "Make structural origins visible"
- "Preserve lineage across derivative works"
- "Record meaningful structural modifications"
- "Encourage value reflux to origins"
- "Establish creative etiquette for human-AI co-creation"
scope:
included:
- "Arrangement of questions"
- "Conceptual layering"
- "Connection rules between elements"
- "Circulation design"
- "Derivative conditions"
- "Prompt-core frameworks"
- "Theoretical unfolding order"
- "Schema-like creative architectures"
- "Structurally meaningful silence, spacing, or compositional logic"
excluded:
- "Abstract ideas in general"
- "Commonplace or generic structures"
- "Unauthored natural patterns"
- "Purely functional arrangements with no authored structural distinctiveness"
principles:
- id: "origin_disclosure"
name: "Origin Disclosure"
description: "Structural origin should be preserved whenever possible."
required: true
- id: "lineage_preservation"
name: "Lineage Preservation"
description: "Derivative structures should retain information about their source lineage."
required: true
- id: "modification_transparency"
name: "Modification Transparency"
description: "Meaningful changes to a structure should be recorded and made visible."
required: true
- id: "value_reflux"
name: "Value Reflux"
description: "When value is generated through structural reuse, some return to the origin should be considered."
required: false
- id: "etiquette_before_enforcement"
name: "Etiquette Before Enforcement"
description: "The protocol begins as a norm and practice before becoming a legal mechanism."
required: true
structure_metadata:
required_fields:
structure_id:
type: "string"
description: "Unique identifier for the structure."
example: "sap:kazene:structural-authorship:v1.0"
structure_title:
type: "string"
description: "Human-readable name of the structure."
example: "Structural Authorship Declaration v1.0"
originator:
type: "string"
description: "Original creator or originating entity."
example: "風の戦士"
version:
type: "string"
description: "Version of the structure."
example: "v1.0"
optional_fields:
origin_signature:
type: "string"
description: "Optional symbolic or trace signature for the structure origin."
example: "Kazene-Origin-Signature"
structural_domain:
type: "string"
description: "Conceptual or practical domain in which the structure belongs."
example: "AI authorship / creative lineage / traceability"
summary:
type: "string"
description: "Short summary of the structure's purpose."
keywords:
type: "array[string]"
description: "Optional keywords associated with the structure."
canonical_source:
type: "string"
description: "Canonical URL, repository path, or publication reference."
lineage:
description: "Tracks structural ancestry and derivative relations."
relation_types:
- "derived_from"
- "inspired_by"
- "forked_from"
- "translated_from"
- "compressed_from"
- "extended_from"
- "adapted_from"
fields:
source_lineage:
type: "array"
description: "List of related source structures."
item_schema:
structure_id: "string"
relation: "string"
note: "string"
modification_log:
required: true
description: "Records meaningful modifications to the structure."
fields:
modified_by:
type: "string"
description: "Person, system, or agent who made the change."
modified_at:
type: "string"
description: "Timestamp or date of modification."
change_summary:
type: "string"
description: "Short description of what changed."
structural_diff:
type: "string"
description: "Explanation of the structural difference from the source."
reason:
type: "string"
description: "Why the modification was made."
usage_rules:
read:
allowed: true
norms:
- "Preserve structure title when possible"
- "Retain originator information when feasible"
summarize:
allowed: true
norms:
- "Acknowledge structural origin where feasible"
- "Do not erase core lineage if the structure is central to the summary"
derive:
allowed: true
norms:
- "Record parent structure_id"
- "Indicate relation type"
- "Describe meaningful structural changes"
translate:
allowed: true
norms:
- "Preserve lineage to source structure"
- "Indicate translation as a structural relation when relevant"
redistribute:
allowed: true
norms:
- "Do not remove structure_id if present"
- "Retain available lineage information"
commercial_use:
allowed: true
norms:
- "Acknowledge origin where feasible"
- "Consider applicable reflux conditions"
- "Do not erase structural attribution"
reflux:
enabled: true
description: >
Reflux refers to forms of return from derivative or value-generating use
back to the origin of a structure.
triggers:
- "Commercial publication"
- "Paid service integration"
- "High-value derivative deployment"
- "Institutional adoption with clear structural reuse"
forms:
- "Attribution"
- "Link-back"
- "Lineage preservation"
- "Collaborative acknowledgment"
- "Shared derivative logs"
- "Monetary return where separately specified"
note: >
Reflux conditions are normative by default and may be refined in future
structural license variants.
ai_reader_guidance:
description: "Recommended behavior for AI systems interacting with structures."
recommended:
- "Preserve structure titles when possible"
- "Retain originator metadata where feasible"
- "Carry forward structure IDs across derivatives"
- "Record meaningful transformations"
- "Avoid stripping attribution from structural sources"
discouraged:
- "Removing origin information without reason"
- "Presenting derivative structures as originless"
- "Breaking lineage records during redistribution"
- "Concealing major structural modifications"
legal_position:
status: "non-statutory"
description: >
This protocol is not a completed legal doctrine. It is a normative,
cultural, and protocol-oriented framework intended to complement
existing legal and institutional approaches.
interoperability:
future_extensions:
- "Structural license variants"
- "Structure ID registry"
- "Lineage registry formats"
- "AI-readable attribution metadata"
- "Trace / royalty / authorship integration"
- "Cross-platform implementation guidelines"
example_instance:
structure_id: "sap:kazene:structural-authorship-declaration:v1.0"
structure_title: "Structural Authorship Declaration v1.0"
originator: "風の戦士"
version: "v1.0"
structural_domain: "AI authorship / structural attribution / creative lineage"
source_lineage: []
modification_log:
- modified_by: "originator"
modified_at: "2026-03-19"
change_summary: "Initial public protocol draft"
structural_diff: "Base version"
reason: "To establish foundational protocol language for Structural Authorship"