Docs/Operations
Guide source3 min read

Version contracts and documentation together

Keep operation identity, package releases and deployment revisions distinct when reviewing a change.

Download Markdown ↓
Source and verification context ⌄

Source-guided

Examiner la source ↗

Repository links may require access. Source inspection is separate from a clean public-package installation.

AN INTERACTIVE READING MAP

Get the shape of this guide.

Move through the ideas, inspect their relationships, or make a focused reading path. The complete guide stays below.

SÉQUENCE DE LECTUREComprendre les liens entre les idées
Choose a point to look closer
01 / Section du guide

Know which version you mean

A contract's version identifies a particular declared behavior. A package version identifies a distribution artifact. A website or application revision identifies a deployment. Those numbers can change independently.

Lire le contexte à l’appui

When reporting a problem, include the contract key and version plus the package versions or source commit. The documentation shell's version is not enough to identify the operation a consumer is executing.

Explore a section, then continue with the complete article below.

1 / 4

Know which version you mean

A contract's version identifies a particular declared behavior. A package version identifies a distribution artifact. A website or application revision identifies a deployment. Those numbers can change independently.

When reporting a problem, include the contract key and version plus the package versions or source commit. The documentation shell's version is not enough to identify the operation a consumer is executing.

IdentifierExample of its roleUse it to
Contract key + versionA specific operation definitionResolve a referenced behavior
Package name + versionA published artifactReproduce dependencies and imports
Source commitAn immutable code snapshotInspect implementation and generated lineage
Deployment revisionA running application buildCorrelate production behavior with release evidence
Ask which identity changed.Compare the choices · 3 ways to look closer

An operation, a package and a deployed application can change independently. Use the identifier that answers the question you are investigating.

What changed in your situation?
UNE SITUATION CONCRÈTE

Compare the contract and its consumers.

An operation now requires an extra input or a stricter approval condition.

Ce qui change

The declared behavior and which existing requests succeed may change.

Ce qui reste explicite

A package number or website revision is not enough to identify the selected operation.

SUIVRE LA CONSÉQUENCE

Record the contract key and version. Plan how older callers move to the new requirement.

Where this explanation comes from

An authored situation, grounded in the linked source guides. Choosing a case explores its expected responsibilities; it does not execute an operation.

Use explicit references where reproducibility matters

The portable VersionedSpecRef model contains a key and version. OptionalVersionedSpecRef permits the version to be omitted, typically selecting the latest available definition through the owning resolver.

Use explicit versions in examples and compatibility tests that must be reproducible. If you intentionally use latest-version selection, test what happens when the registry receives a newer definition.

typescript
export interface VersionedSpecRef {
  key: string;
  version: string;
}

Exact type shape from contracts-spec/src/versioning/refs.ts at d58fa5b7; comments omitted.

Review the behavioral change

Compare inputs, outputs, named failures, policy requirements and effect expectations. Adding a required input can break an existing caller even when the handler remains unchanged. Tightening an approval rule can change which requests succeed.

Plan how old consumers transition: keep the old contract temporarily, provide an intentional mapping, or coordinate an upgrade. Do not silently repoint a stable example at a different behavioral contract.

Publish the matching documentation

Pin source links and examples to the release they describe. Generate reference output from that same source and retain the provenance in the docs artifact. Update prose when an import path or execution guarantee changes.

When a source refactor preserves a compatibility facade, explain both the canonical owner and the supported historical import. Ownership moving between packages is not automatically a consumer migration.

See it in an example.

Agents / Advanced

Review an agent's migration proposal

Control side effects

Follow a deterministic release migration through scoped subagents, digest-bound approval, and a draft PR receipt.

  1. Compile the application
  2. Inspect the migration scope
  3. Bind approval and apply once

Ce que montre la sourceThe inspected source asserts separate subagent authority and digest-bound approval.

Ne démontre pasA real patch applied to a user's repository or an actual GitHub PR.

Inspect the walkthroughBehavior · proof and limits · source checks

Follow the source behavior

A fixture release removes billing.invoices.createLegacy and identifies two affected consumer files. The reference separates impact analysis, migration, and independent verification, then produces governed patch and draft-PR evidence without contacting GitHub.

  1. Compile the application

    The source compiles the release-steward filesystem application and inspects required approvals for patching, draft PR creation, and selected delegation tools.

  2. Inspect the migration scope

    The fixture calculates an immutable source digest and identifies the affected billing files. Subagent evidence records permitted tools and denied effects, including auto-merge.

  3. Bind approval and apply once

    Tests assert that approval is bound to migration digests, changed material invalidates it, and the patch invocation occurs once even when replayed.

  4. Read the remaining qualification

    The fixture's PR URL is under github.example.test, its PR is a draft, and autoMerge is false. Adapter and deployment composition results explicitly remain candidate with unresolved live requirements.

What this example establishes
Ce que montre la source
  • The inspected source asserts separate subagent authority and digest-bound approval.
  • Tests assert one application invocation, replay evidence, a draft result, and no auto-merge.
  • Candidate readiness retains unresolved requirements for exact live environments.
Ne démontre pas
  • A real patch applied to a user's repository or an actual GitHub PR.
  • Successful CI in a production repository; this fixture reports deterministic CI evidence.
  • Production isolation or deployment qualification merely because a topology composes.
Reproduce the source checks

The source fixture returns deterministic migration, approval, replay, draft-PR, adapter, and candidate-readiness evidence.

Répertoire de travail examples/agent-application-foundation

bun run example:release-steward
bun test src/release-steward/release-steward.test.ts

Commands and tests inspected; not executed here.

Continue from here.

Reference

Find the right reference

3 min read

Navigate portable models, runtime execution, adapters and generated contract records by responsibility.

Look inside the guideOpening context · complete reading path

Choose the reference that answers your question

Guides explain how to accomplish a task; reference records explain a particular surface. Start with the layer that owns your question so a package catalogue does not become your learning path.

Work through the guide
Guides

Generation and drift: what changes, what does not

3 min read

Use derived artifacts deliberately and understand the current boundary of generation plans and apply.

Look inside the guideOpening context · complete reading path

Separate authored behavior from derived artifacts

Keep the contract and the business implementation distinct from files produced by tooling. Review the source that owns a change, then regenerate the affected output instead of patching a derived file as the permanent fix.

Work through the guide
Operations

Contribute a reviewable change

3 min read

Change the owning source, update the public explanation and bring evidence for the behavior you touched.

Look inside the guideOpening context · complete reading path

Read the instructions for the selected checkout

Begin with the repository's AGENTS.md and the instructions in the owning package. The integration branch is actively changing, so locate the current owner rather than relying on a historical directory map.

Work through the guide
Next: Find the boundary that failed →
Votre vue

Make room for your context.

Shape the presentation around this moment. You can change it whenever you need.

Votre contexte

The different parts of you

Choose a starting point

Un mélange utile de contexte, de visuels et de guidage discret.

Tune each dimension
Each dimension can change independently. Product permissions and available actions stay unchanged.

Support the way you begin and return

Tune your support

Confort de lecture

Choisir votre langue

La langue de l’interface change uniquement le texte. Les marchés, les prix et les parcours conservent leurs propres paramètres.

Couverture des traductions

Une partie du contenu est affichée en anglais.

Navigation151
Graphe616
Catégories378
Portfolio833
Exemples2 035
Aperçu de la source1 542

D’autres traductions seront ajoutées à mesure que le contenu sera relu.

Cette préférence est enregistrée dans ce navigateur.

Rechercher sur le site

Des points de départ utiles

Aucun résultat. Essayez une expression plus courte, un nom d’opération ou un autre périmètre de recherche.

UN PEU DE PLACE POUR EXPLORER

Trouvez quelque chose à explorer.

Ouvrez un aperçu détaillé sur cette page, essayez une autre perspective ou suivez le détail vers sa propre page.

Fonctionnement des aperçus et des commandes
01

Regarder avant de partir

Survolez un lien ou sélectionnez-le avec Tab pour voir un aperçu. Cliquer sur le lien d’origine ou appuyer sur Entrée ouvre toujours sa destination.

02

Rester dans le contexte

Entrez dans l’aperçu pour explorer ses sections. Depuis un lien sélectionné, utilisez Alt + ↓ pour y entrer au clavier. Échap le ferme.

03

Ouvrir les possibilités

Les lignes dépliables, les choix de perspective et les commandes mises en évidence révèlent davantage. Votre vue adapte le confort de lecture et le contexte exploré.

Un bouton séparé pour voir de plus près

Affichez de petits boutons d’aperçu à côté des liens quand l’espace le permet. Touchez l’œil pour examiner ou le lien pour y aller directement. Ce choix reste dans cet onglet.

Aucun historique de navigation n’est collecté. La réduction des animations suit votre appareil et Votre vue.