Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions 1-formats/a2ml/anchor/README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
*DRAFT* — Version {version}. Migrated from the superseded A2ML format
family to the DEED/K9 ecosystem. Not yet ratified.

Normative grammar: link:grammars/anchor.abnf[anchor.abnf] (v1.0.0 DRAFT).
Normative grammar: link:abnf/anchor.abnf[anchor.abnf] (v1.0.0 DRAFT).

== What Is ANCHOR?

Expand All @@ -30,7 +30,7 @@ directives to close the gap.
projection of a repo's actual state. The fiber over a declaration is
everything the projection lost. ANCHOR is the point where the two are
forced back together. See
link:../deed/spec/DEED-GRAMMAR-SPEC.adoc#echo[DEED spec §7.2.3].
link:../../deed/spec/DEED-GRAMMAR-SPEC.adoc#echo[DEED spec §7.2.3].
====

== What ANCHOR Is NOT
Expand Down Expand Up @@ -247,11 +247,11 @@ formats are *superseded*. Migration steps:

== See Also

* link:grammars/anchor.abnf[ANCHOR ABNF Grammar]
* link:abnf/anchor.abnf[ANCHOR ABNF Grammar]
* link:spec/ANCHOR-FORMAT-SPEC.adoc[ANCHOR Format Specification]
* link:../deed/spec/DEED-GRAMMAR-SPEC.adoc[DEED Grammar Specification]
* link:../../deed/spec/DEED-GRAMMAR-SPEC.adoc[DEED Grammar Specification]
(parent lexical layer, echo typing)
* link:../k9-coordination-protocol/specs/K9-COORDINATION-SPEC.adoc[K9 Coordination Specification]
* link:../../../2-protocols/k9-coordination/spec/COORDINATION-K9-SPEC.adoc[K9 Coordination Specification]
(operational surface ANCHOR may direct updates to)

== Licence
Expand Down
28 changes: 18 additions & 10 deletions 1-formats/deed/README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -16,17 +16,25 @@ Prepared 2026-09-08. Alignment revision: 0.2.0.

This is the specification the owner asked for as top priority. It is
deliberately scoped to the surface and its identity rule, because that is
what unblocks the `.a2ml` → `.deed` conversion (#64) and the downstream
what unblocks the `.a2ml` → `.deed` conversion (#837) and the downstream
consumers. The typing chapter (<<typechecking>>) is marked PROPOSED
throughout and is *not* part of the v0.1 conformance surface.

*Normative grammar:* link:../abnf/deed.abnf[abnf/deed.abnf] is normative for
*Normative grammar:* link:spec/abnf/deed.anbf[abnf/deed.anbf] is normative for
parsing. The EBNF in <<concrete-syntax>> is informative.
+
NOTE (standards#837): the grammar currently ships as TWO files —
this one (declares v1.0.0; typo'd `.anbf` extension) and the sibling archive
`deed.abnf_v1.0` (misnamed: its content is v0.1.0 DRAFT, mirroring
`DEED-GRAMMAR-SPEC_v0.1.adoc`). Links below resolve to the file holding the
cited content. The campaign's held grammar-hygiene step declares ONE
normative file; until that owner ruling, `deed.anbf` carries the most
recent grammar.

Compatible with:

* link:../abnf/deed.abnf[DEED ABNF v0.1.0 DRAFT] (as amended by the alignment errata)
* link:../specs/K9-COORDINATION-SPEC.adoc[K9 Coordination Spec] (separate surface;
* link:spec/abnf/deed.abnf_v1.0[DEED ABNF v0.1.0 DRAFT (file `deed.abnf_v1.0`; misnamed, content is v0.1.0)] (as amended by the alignment errata)
* link:../../2-protocols/k9-coordination/spec/COORDINATION-K9-SPEC.adoc[K9 Coordination Spec] (separate surface;
DEED does not parse `.k9`)

== Changelog
Expand Down Expand Up @@ -109,7 +117,7 @@ INVALID). Parsers MUST be deterministic given identical input bytes.
Keywords, document heads, booleans, UUID prefixes, filename dispatch
literals, and string-escape letters are *case-sensitive*. `repo-deed` is
valid; `REPO-DEED` is not. `#t` is valid; `#T` is not. This matches RFC 7405
`%s"..."` literals in link:../abnf/deed.abnf[deed.abnf].
`%s"..."` literals in link:spec/abnf/deed.anbf[deed.anbf].

[cols="1,3"]
|===
Expand Down Expand Up @@ -174,7 +182,7 @@ speciation artefact, not a deed.
== Concrete syntax

The productions below are *informative EBNF*. If they disagree with
link:../abnf/deed.abnf[abnf/deed.abnf], the ABNF wins.
link:spec/abnf/deed.anbf[abnf/deed.anbf], the ABNF wins.

----
Deed ::= Header Sep? Form Sep? EOF
Expand Down Expand Up @@ -305,7 +313,7 @@ implementation MUST test the exact name `estate_chora.deed` BEFORE the
[NOTE]
====
ABNF cannot express negation, so this exclusion is a side condition in
both this document and `abnf/deed.abnf`. The side condition is normative:
both this document and `abnf/deed.anbf`. The side condition is normative:
the grammar alone is not sufficient to dispatch a filename.
====

Expand Down Expand Up @@ -748,7 +756,7 @@ unnoticed, and it must not carry over to `.deed`.

A `.deed` file in `strict` mode MUST:

. Parse completely against `abnf/deed.abnf` (full input consumed).
. Parse completely against `abnf/deed.anbf` (full input consumed).
. Have a filename that dispatches to a head matching `DocHead`.
. Carry the required identity fields in the table in <<identity>>.
. Not use `_` in any symbol, `#T`/`#F` as booleans, or unknown escapes.
Expand Down Expand Up @@ -859,10 +867,10 @@ locally. Either the estate chora gains it, or `extends-vocabulary` lands.

== References

* link:../abnf/deed.abnf[DEED ABNF]
* link:spec/abnf/deed.anbf[DEED ABNF (v1.0.0, file `deed.anbf`)]
* link:https://www.rfc-editor.org/rfc/rfc7405[RFC 7405] (case-sensitive ABNF strings)
* link:https://www.rfc-editor.org/rfc/rfc4122[RFC 4122] §4.3 (UUID v5)
* link:../specs/K9-COORDINATION-SPEC.adoc[K9 Coordination File Specification]
* link:../../2-protocols/k9-coordination/spec/COORDINATION-K9-SPEC.adoc[K9 Coordination File Specification]
(operational surface; not this grammar)

== License
Expand Down
28 changes: 18 additions & 10 deletions 1-formats/deed/spec/DEED-GRAMMAR-SPEC.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -16,17 +16,25 @@ Prepared 2026-09-08. Alignment revision: 0.2.0.

This is the specification the owner asked for as top priority. It is
deliberately scoped to the surface and its identity rule, because that is
what unblocks the `.a2ml` → `.deed` conversion (#64) and the downstream
what unblocks the `.a2ml` → `.deed` conversion (#837) and the downstream
consumers. The typing chapter (<<typechecking>>) is marked PROPOSED
throughout and is *not* part of the v0.1 conformance surface.

*Normative grammar:* link:../abnf/deed.abnf[abnf/deed.abnf] is normative for
*Normative grammar:* link:./abnf/deed.anbf[abnf/deed.anbf] is normative for
parsing. The EBNF in <<concrete-syntax>> is informative.
+
NOTE (standards#837): the grammar currently ships as TWO files —
this one (declares v1.0.0; typo'd `.anbf` extension) and the sibling archive
`deed.abnf_v1.0` (misnamed: its content is v0.1.0 DRAFT, mirroring
`DEED-GRAMMAR-SPEC_v0.1.adoc`). Links below resolve to the file holding the
cited content. The campaign's held grammar-hygiene step declares ONE
normative file; until that owner ruling, `deed.anbf` carries the most
recent grammar.

Compatible with:

* link:../abnf/deed.abnf[DEED ABNF v0.1.0 DRAFT] (as amended by the alignment errata)
* link:../specs/K9-COORDINATION-SPEC.adoc[K9 Coordination Spec] (separate surface;
* link:./abnf/deed.abnf_v1.0[DEED ABNF v0.1.0 DRAFT (file `deed.abnf_v1.0`; misnamed, content is v0.1.0)] (as amended by the alignment errata)
* link:../../../2-protocols/k9-coordination/spec/COORDINATION-K9-SPEC.adoc[K9 Coordination Spec] (separate surface;
DEED does not parse `.k9`)

== Changelog
Expand Down Expand Up @@ -109,7 +117,7 @@ INVALID). Parsers MUST be deterministic given identical input bytes.
Keywords, document heads, booleans, UUID prefixes, filename dispatch
literals, and string-escape letters are *case-sensitive*. `repo-deed` is
valid; `REPO-DEED` is not. `#t` is valid; `#T` is not. This matches RFC 7405
`%s"..."` literals in link:../abnf/deed.abnf[deed.abnf].
`%s"..."` literals in link:./abnf/deed.anbf[deed.anbf].

[cols="1,3"]
|===
Expand Down Expand Up @@ -174,7 +182,7 @@ speciation artefact, not a deed.
== Concrete syntax

The productions below are *informative EBNF*. If they disagree with
link:../abnf/deed.abnf[abnf/deed.abnf], the ABNF wins.
link:./abnf/deed.anbf[abnf/deed.anbf], the ABNF wins.

----
Deed ::= Header Sep? Form Sep? EOF
Expand Down Expand Up @@ -305,7 +313,7 @@ implementation MUST test the exact name `estate_chora.deed` BEFORE the
[NOTE]
====
ABNF cannot express negation, so this exclusion is a side condition in
both this document and `abnf/deed.abnf`. The side condition is normative:
both this document and `abnf/deed.anbf`. The side condition is normative:
the grammar alone is not sufficient to dispatch a filename.
====

Expand Down Expand Up @@ -748,7 +756,7 @@ unnoticed, and it must not carry over to `.deed`.

A `.deed` file in `strict` mode MUST:

. Parse completely against `abnf/deed.abnf` (full input consumed).
. Parse completely against `abnf/deed.anbf` (full input consumed).
. Have a filename that dispatches to a head matching `DocHead`.
. Carry the required identity fields in the table in <<identity>>.
. Not use `_` in any symbol, `#T`/`#F` as booleans, or unknown escapes.
Expand Down Expand Up @@ -859,10 +867,10 @@ locally. Either the estate chora gains it, or `extends-vocabulary` lands.

== References

* link:../abnf/deed.abnf[DEED ABNF]
* link:./abnf/deed.anbf[DEED ABNF (v1.0.0, file `deed.anbf`)]
* link:https://www.rfc-editor.org/rfc/rfc7405[RFC 7405] (case-sensitive ABNF strings)
* link:https://www.rfc-editor.org/rfc/rfc4122[RFC 4122] §4.3 (UUID v5)
* link:../specs/K9-COORDINATION-SPEC.adoc[K9 Coordination File Specification]
* link:../../../2-protocols/k9-coordination/spec/COORDINATION-K9-SPEC.adoc[K9 Coordination File Specification]
(operational surface; not this grammar)

== License
Expand Down
7 changes: 6 additions & 1 deletion 1-formats/deed/spec/abnf/deed.abnf_v1.0
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,13 @@
; SPDX-License-Identifier: CC-BY-SA-4.0
;
; DEED grammar, v0.1.0 DRAFT
; Normative for parsing. Prose and rationale: ../DEED-GRAMMAR-SPEC.adoc
; Normative for parsing (for v0.1.0-era deeds). Prose and rationale: ../DEED-GRAMMAR-SPEC.adoc
;
; NOTICE (standards#837): FILENAME MISNOMER — this file is the v0.1 DRAFT
; archive (its content declares v0.1.0; the "_v1.0" suffix contradicts the
; content, mirroring the correctly-named DEED-GRAMMAR-SPEC_v0.1.adoc). The
; later v1.0.0 revision is deed.anbf in this directory. Grammar below is
; unchanged.
; NOTE: there is no "key = value" production and no "[section]" production.
; The only bracket is "(". A file using "=" is not a deed.

Expand Down
6 changes: 6 additions & 0 deletions 1-formats/deed/spec/abnf/deed.anbf
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,12 @@
; DEED grammar, v1.0.0
; Normative for parsing. Prose and rationale: ../DEED-GRAMMAR-SPEC.adoc
;
; NOTICE (standards#837): this file is the LATER v1.0.0 revision, but its
; extension is typo'd (.anbf) — documents linked "abnf/deed.abnf" while the
; v0.1.0 archive sat misnamed as deed.abnf_v1.0. As of 2026-09-17 the docs
; resolve to this file directly. The campaign's held grammar-hygiene step
; declares ONE normative file (this content, most likely renamed deed.abnf)
; pending owner ruling. Grammar below is unchanged.
; Requires RFC 7405 (%s"..." case-sensitive string literals).
;
; NOTE: there is no "key = value" production and no "[section]" production.
Expand Down
Loading