specfuse-authoring 0.3.1__tar.gz

specfuse_authoring-0.3.1/.gitignore

@@ -0,0 +1,23 @@
+.DS_Store
+*.swp
+*.swo
+.idea/
+.vscode/
+node_modules/
+.env
+.env.local
+output/
+*.log
+*.iml
+
+# Python packaging
+__pycache__/
+*.py[cod]
+build/
+dist/
+*.egg-info/
+.venv/
+venv/
+# Spectral bundle artifacts
+*.bundle.yaml
+.bundle.yaml

specfuse_authoring-0.3.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

specfuse_authoring-0.3.1/NOTICE

@@ -0,0 +1,6 @@
+Specfuse Spec-Authoring Kit
+Copyright 2026 Specfuse contributors
+
+This product is part of the Specfuse methodology suite
+(https://github.com/specfuse). It is licensed under the Apache License,
+Version 2.0. See the LICENSE file for the full text.

specfuse_authoring-0.3.1/PKG-INFO

@@ -0,0 +1,103 @@
+Metadata-Version: 2.4
+Name: specfuse-authoring
+Version: 0.3.1
+Summary: Specfuse authoring kit: handbooks, samples, Claude assets, project bootstrap, and the generator launcher.
+Project-URL: Homepage, https://github.com/Specfuse/authoring
+Project-URL: Source, https://github.com/Specfuse/authoring
+Author: Christian Labonté
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: arazzo,asyncapi,codegen,openapi,spec-driven,specfuse
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Code Generators
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# Specfuse Spec-Authoring Kit
+
+The upstream contract for [Specfuse](https://github.com/Specfuse) projects. Defines the conventions, vendor extensions, and authoring workflows that the Specfuse code generator consumes to produce backend, frontend, and worker artifacts from OpenAPI 3.0.3 + AsyncAPI 3.0.0 + Arazzo 1.0.1 specifications.
+
+## Quick start
+
+Bootstrap a new Specfuse project with the kit's CLI:
+
+```bash
+pipx install specfuse-authoring     # CLI; recommended
+#   (or, inside a venv you control: python3 -m pip install specfuse-authoring)
+specfuse-authoring init ~/projects/my-new-project
+```
+
+You'll be prompted for the project name, the project token (channel-address prefix), and the initial domain. The CLI substitutes placeholders, scaffolds the authoring contract (handbooks + samples) into `.specfuse/authoring/`, wires the `specfuse-authoring` Claude Code plugin into `.claude/settings.json`, and prints next steps. Pass `--name`/`--token`/`--domain` to run non-interactively.
+
+The Claude Code authoring assets (skills + agents) ship as the `specfuse-authoring` plugin in the shared `specfuse` marketplace. `init` auto-wires the plugin, but you install it once in Claude Code with:
+
+```
+/plugin marketplace add specfuse/specfuse
+/plugin install specfuse-authoring@specfuse
+```
+
+To re-sync `.specfuse/authoring/` and re-assert the plugin config in an existing project after a kit update:
+
+```bash
+specfuse-authoring refresh ~/projects/existing-project
+```
+
+Pull newer skills with `/plugin update specfuse-authoring@specfuse`.
+
+See [`examples/hello-orders/`](examples/hello-orders/) for a complete worked example.
+
+## What's in the kit
+
+| Asset | Contents |
+|---|---|
+| **Handbooks** ([`handbooks/`](handbooks/)) | 6 authoritative documents: REST API, AsyncAPI, Arazzo, vendor extensions, AI access policy framework, and the generator's project file. Together these define the full spec-authoring contract. |
+| **Samples** ([`samples/`](samples/)) | 4 canonical YAML templates — endpoints, async messages, scenarios, recipes — that every authored file should pattern-match against. |
+| **Schemas** ([`schemas/`](schemas/)) | Working Spectral rulesets and custom functions for validation under `schemas/spectral/`. CI lints the bundled example against them. |
+| **Templates** ([`templates/`](templates/)) | The `project-init/` skeleton, plus the AI Access Policy template. |
+| **Claude assets** | 5 Claude Code sub-agents and 20 authoring skills (`/specfuse-authoring:design-scenario`, `/specfuse-authoring:design-async`, `/specfuse-authoring:design-recipe`, etc.) that automate spec design. Distributed as the `specfuse-authoring` plugin in the `specfuse/specfuse` marketplace; `init` wires the plugin and scaffolds the contract the skills read into `.specfuse/authoring/`. |
+| **Bundled example** ([`examples/hello-orders/`](examples/hello-orders/)) | A 61-file complete Specfuse project — 2 domains, 3 entities, 1 state-transition event, 1 cross-domain scenario, 2 setup recipes, filled AI access policy, CI workflow. Serves as the kit's regression net. |
+
+## Where to start
+
+| You want to… | Read first | Then run |
+|---|---|---|
+| Bootstrap a new project | [`docs/getting-started.md`](docs/getting-started.md) | `specfuse-authoring init <target-dir>` |
+| Design your first scenario | [`handbooks/Arazzo_Handbook.md`](handbooks/Arazzo_Handbook.md) | `/specfuse-authoring:design-scenario` |
+| Author a new entity or endpoint | [`handbooks/API_Handbook.md`](handbooks/API_Handbook.md) + [`samples/endpoint-samples.yaml`](samples/endpoint-samples.yaml) | (no kit command yet — author by hand) |
+| Design an async event or scheduled job | [`handbooks/AsyncAPI_Handbook.md`](handbooks/AsyncAPI_Handbook.md) + [`samples/message-samples.yaml`](samples/message-samples.yaml) | `/specfuse-authoring:design-async` |
+| Add a setup recipe | [`handbooks/Arazzo_Handbook.md`](handbooks/Arazzo_Handbook.md) §7 + [`samples/recipe-samples.yaml`](samples/recipe-samples.yaml) | `/specfuse-authoring:design-recipe` |
+| Configure AI agent access | [`handbooks/AI_Access_Policy_Framework.md`](handbooks/AI_Access_Policy_Framework.md) + [`templates/ai-access-policy-template.md`](templates/ai-access-policy-template.md) | (copy template into project) |
+| Look up a `x-*` extension | [`handbooks/Vendor_Extensions.md`](handbooks/Vendor_Extensions.md) | — |
+| Configure the generator project file | [`handbooks/Project_File.md`](handbooks/Project_File.md) | — |
+| See a complete worked example | [`examples/hello-orders/README.md`](examples/hello-orders/README.md) | — |
+
+## Relationship to other Specfuse repos
+
+```
+spec-authoring-kit  ◄── this repo (rules, samples, templates)
+       ▲
+       │ consumes
+       │
+   ┌───┴────────────────┐
+   │                    │
+generator           orchestrator
+(Java/Kotlin —      (filesystem-based
+ produces code      multi-agent workflow
+ from specs)        coordination)
+```
+
+The kit is upstream of both: it defines *what* a Specfuse spec must look like. The generator consumes those specs to emit code. The orchestrator coordinates the multi-agent authoring workflow that produces those specs.
+
+## Status
+
+**Incubating** (`v0.3.1`), Apache-2.0. Handbooks, samples, schemas, the `project-init` template, the bundled `hello-orders` example, the `specfuse-authoring` plugin (in the `specfuse/specfuse` marketplace), and the `specfuse-authoring` CLI are all in place. Generator-side alignment items are tracked in [`compatibility.md`](compatibility.md#outstanding-generator-side-follow-ups).
+
+The kit is distributed on PyPI as `specfuse-authoring` and hosted under [`Specfuse/authoring`](https://github.com/Specfuse/authoring). The code generator it drives is distributed separately as a pinned, checksum-verified release asset (see [`generator.lock`](generator.lock)); `specfuse-authoring generate` resolves, verifies, and runs it on demand.
+
+## Additional references
+
+- [`compatibility.md`](compatibility.md) — kit ↔ generator version matrix and outstanding generator-side follow-ups.
+- [`provenance.md`](provenance.md) — bug-and-PR history that motivated each vendor extension. Kit-maintainer audit trail; external consumers do not need the referenced PRs to resolve.

specfuse_authoring-0.3.1/README.md

@@ -0,0 +1,85 @@
+# Specfuse Spec-Authoring Kit
+
+The upstream contract for [Specfuse](https://github.com/Specfuse) projects. Defines the conventions, vendor extensions, and authoring workflows that the Specfuse code generator consumes to produce backend, frontend, and worker artifacts from OpenAPI 3.0.3 + AsyncAPI 3.0.0 + Arazzo 1.0.1 specifications.
+
+## Quick start
+
+Bootstrap a new Specfuse project with the kit's CLI:
+
+```bash
+pipx install specfuse-authoring     # CLI; recommended
+#   (or, inside a venv you control: python3 -m pip install specfuse-authoring)
+specfuse-authoring init ~/projects/my-new-project
+```
+
+You'll be prompted for the project name, the project token (channel-address prefix), and the initial domain. The CLI substitutes placeholders, scaffolds the authoring contract (handbooks + samples) into `.specfuse/authoring/`, wires the `specfuse-authoring` Claude Code plugin into `.claude/settings.json`, and prints next steps. Pass `--name`/`--token`/`--domain` to run non-interactively.
+
+The Claude Code authoring assets (skills + agents) ship as the `specfuse-authoring` plugin in the shared `specfuse` marketplace. `init` auto-wires the plugin, but you install it once in Claude Code with:
+
+```
+/plugin marketplace add specfuse/specfuse
+/plugin install specfuse-authoring@specfuse
+```
+
+To re-sync `.specfuse/authoring/` and re-assert the plugin config in an existing project after a kit update:
+
+```bash
+specfuse-authoring refresh ~/projects/existing-project
+```
+
+Pull newer skills with `/plugin update specfuse-authoring@specfuse`.
+
+See [`examples/hello-orders/`](examples/hello-orders/) for a complete worked example.
+
+## What's in the kit
+
+| Asset | Contents |
+|---|---|
+| **Handbooks** ([`handbooks/`](handbooks/)) | 6 authoritative documents: REST API, AsyncAPI, Arazzo, vendor extensions, AI access policy framework, and the generator's project file. Together these define the full spec-authoring contract. |
+| **Samples** ([`samples/`](samples/)) | 4 canonical YAML templates — endpoints, async messages, scenarios, recipes — that every authored file should pattern-match against. |
+| **Schemas** ([`schemas/`](schemas/)) | Working Spectral rulesets and custom functions for validation under `schemas/spectral/`. CI lints the bundled example against them. |
+| **Templates** ([`templates/`](templates/)) | The `project-init/` skeleton, plus the AI Access Policy template. |
+| **Claude assets** | 5 Claude Code sub-agents and 20 authoring skills (`/specfuse-authoring:design-scenario`, `/specfuse-authoring:design-async`, `/specfuse-authoring:design-recipe`, etc.) that automate spec design. Distributed as the `specfuse-authoring` plugin in the `specfuse/specfuse` marketplace; `init` wires the plugin and scaffolds the contract the skills read into `.specfuse/authoring/`. |
+| **Bundled example** ([`examples/hello-orders/`](examples/hello-orders/)) | A 61-file complete Specfuse project — 2 domains, 3 entities, 1 state-transition event, 1 cross-domain scenario, 2 setup recipes, filled AI access policy, CI workflow. Serves as the kit's regression net. |
+
+## Where to start
+
+| You want to… | Read first | Then run |
+|---|---|---|
+| Bootstrap a new project | [`docs/getting-started.md`](docs/getting-started.md) | `specfuse-authoring init <target-dir>` |
+| Design your first scenario | [`handbooks/Arazzo_Handbook.md`](handbooks/Arazzo_Handbook.md) | `/specfuse-authoring:design-scenario` |
+| Author a new entity or endpoint | [`handbooks/API_Handbook.md`](handbooks/API_Handbook.md) + [`samples/endpoint-samples.yaml`](samples/endpoint-samples.yaml) | (no kit command yet — author by hand) |
+| Design an async event or scheduled job | [`handbooks/AsyncAPI_Handbook.md`](handbooks/AsyncAPI_Handbook.md) + [`samples/message-samples.yaml`](samples/message-samples.yaml) | `/specfuse-authoring:design-async` |
+| Add a setup recipe | [`handbooks/Arazzo_Handbook.md`](handbooks/Arazzo_Handbook.md) §7 + [`samples/recipe-samples.yaml`](samples/recipe-samples.yaml) | `/specfuse-authoring:design-recipe` |
+| Configure AI agent access | [`handbooks/AI_Access_Policy_Framework.md`](handbooks/AI_Access_Policy_Framework.md) + [`templates/ai-access-policy-template.md`](templates/ai-access-policy-template.md) | (copy template into project) |
+| Look up a `x-*` extension | [`handbooks/Vendor_Extensions.md`](handbooks/Vendor_Extensions.md) | — |
+| Configure the generator project file | [`handbooks/Project_File.md`](handbooks/Project_File.md) | — |
+| See a complete worked example | [`examples/hello-orders/README.md`](examples/hello-orders/README.md) | — |
+
+## Relationship to other Specfuse repos
+
+```
+spec-authoring-kit  ◄── this repo (rules, samples, templates)
+       ▲
+       │ consumes
+       │
+   ┌───┴────────────────┐
+   │                    │
+generator           orchestrator
+(Java/Kotlin —      (filesystem-based
+ produces code      multi-agent workflow
+ from specs)        coordination)
+```
+
+The kit is upstream of both: it defines *what* a Specfuse spec must look like. The generator consumes those specs to emit code. The orchestrator coordinates the multi-agent authoring workflow that produces those specs.
+
+## Status
+
+**Incubating** (`v0.3.1`), Apache-2.0. Handbooks, samples, schemas, the `project-init` template, the bundled `hello-orders` example, the `specfuse-authoring` plugin (in the `specfuse/specfuse` marketplace), and the `specfuse-authoring` CLI are all in place. Generator-side alignment items are tracked in [`compatibility.md`](compatibility.md#outstanding-generator-side-follow-ups).
+
+The kit is distributed on PyPI as `specfuse-authoring` and hosted under [`Specfuse/authoring`](https://github.com/Specfuse/authoring). The code generator it drives is distributed separately as a pinned, checksum-verified release asset (see [`generator.lock`](generator.lock)); `specfuse-authoring generate` resolves, verifies, and runs it on demand.
+
+## Additional references
+
+- [`compatibility.md`](compatibility.md) — kit ↔ generator version matrix and outstanding generator-side follow-ups.
+- [`provenance.md`](provenance.md) — bug-and-PR history that motivated each vendor extension. Kit-maintainer audit trail; external consumers do not need the referenced PRs to resolve.

specfuse_authoring-0.3.1/examples/hello-orders/README.md

@@ -0,0 +1,55 @@
+# hello-orders
+
+A tiny, complete Specfuse example project bundled inside the [spec-authoring-kit](https://github.com/Specfuse/authoring). Its job is two-fold:
+
+1. **Pedagogical** — show, in one place, what a minimum-but-real Specfuse project looks like across OpenAPI, AsyncAPI, and Arazzo.
+2. **Regression net** — the kit's CI workflow re-validates this example on every PR; if a handbook change breaks the example, the PR fails.
+
+## What this demonstrates
+
+| Surface | What's here |
+|---|---|
+| Domains | `customer`, `order` |
+| Entities | `Customer` (aggregate), `Order` (aggregate), `OrderLine` (entity under Order) |
+| REST operations | List/Get/Create/Update on Customer & Order, lifecycle `placeOrder`, plus List/Add on OrderLine — 11 operations total |
+| Events | `Customer.Created`, `Customer.Updated`, `Order.Created`, `Order.Updated`, `Order.Placed` (state transition), `OrderLine.Created` |
+| Snapshots | `CustomerSnapshot`, `OrderSnapshot`, `OrderLineSnapshot` |
+| Scenarios | One cross-domain scenario — `place-order` (customer adds a line item to a draft order and places it) |
+| Recipes | `minimal-customer` (root) + `customer-with-draft-order` (extends) |
+| AI access policy | One entity per tier (1, 2) plus an empty tier 0/3 — covers the matrix shape |
+| Flow docs | One Mermaid sequence diagram for the place-order flow |
+
+## How to read it
+
+Start at the spec roots and follow the `$ref` graph:
+
+```
+api/specs/v1/openapi.yaml     ← REST root; references domains/{customer,order}/operations/*.yaml
+api/specs/v1/asyncapi.yaml    ← AsyncAPI root; references async-common/channels + per-domain async-operations
+api/specs/v1/scenarios/cross-domain/place-order.arazzo.yaml
+                              ← the one scenario, references the two recipes below
+api/specs/v1/scenarios/setup-recipes/foundational/
+  minimal-customer.recipe.yaml
+  customer-with-draft-order.recipe.yaml
+```
+
+The handbooks at `<kit>/handbooks/` are the authoritative rules; this example is a worked-out application of them.
+
+## What's deliberately NOT here
+
+The example is intentionally tiny. Out of scope:
+
+- **No `Tenant` entity.** `tenantId` is the ambient scope — it appears as a path parameter and on snapshots but no Tenant entity is defined or has its own operations.
+- **No replace/delete operations.** PATCH only — no PUT, no DELETE.
+- **No payment, shipping, fulfillment, or refund flows.** Order has `draft` and `placed` states; everything past `placed` is out of scope.
+- **No scheduled jobs.** Async-operations folder contains `on-*` / `emit-*` only, no `run-*`.
+- **No tier 0 or tier 3 entities** with detailed blocks — the policy matrix shows them as empty rows for completeness.
+- **No `createUser`, `createTenant`, or auth flows.** The recipe takes a fixed `tenantId` input.
+
+When the kit grows new authoring patterns (search endpoints, scheduled jobs, AI workers, etc.), this example will grow alongside.
+
+## Role as the kit's CI regression net
+
+`.github/workflows/example-regen.yml` validates this example on every PR to the kit. The validation today is YAML-only (every `.yaml` file under `api/` must parse). When the kit ships Spectral rulesets and generator integration, that workflow will grow to run Spectral + a full generator regeneration.
+
+When a handbook or sample change forces a structural change here, regenerate the example in the same PR. The diff against the previous version is the proof that the change is non-breaking (or, intentionally, the visible cost of a breaking change).

specfuse_authoring-0.3.1/examples/hello-orders/api/specs/v1/common/schemas/PaginationLinks.yaml

@@ -0,0 +1,8 @@
+type: object
+description: HATEOAS pagination links for a paged collection response.
+properties:
+  self:  { type: string, format: uri }
+  first: { type: string, format: uri }
+  prev:  { type: string, format: uri }
+  next:  { type: string, format: uri }
+  last:  { type: string, format: uri }

specfuse_authoring-0.3.1/generator.lock

@@ -0,0 +1,12 @@
+{
+  "kit_version": "0.3.1",
+  "min_java": 17,
+  "generator": {
+    "version": "0.1.0",
+    "asset": "specfuse-generator-0.1.0.jar",
+    "sha256": "35dad9afc7c52b6d46b731e1918725de27c451edd2a0407d2c5025c555959838",
+    "release_repo": "Specfuse/generator-dist",
+    "release_tag": "v0.1.0"
+  },
+  "_note": "Pin the kit<->generator contract here. On each generator release: set version/asset/sha256/release_tag, then publish a matching kit patch. sha256=PENDING means no generator is bundled yet; `specfuse-authoring generate` will refuse with a clear message until a real jar is pinned."
+}