Skip to main content

Application documentation

Use this handbook to run, change, and operate the application in this checkout. Read the application profile for purpose and ownership. Contributors follow the project conventions and documentation rules.

Start here​

TaskGuide
Run locallySet up the environment, then start and check readiness
Implement a featureFollow the implementation workflow
Test a changeChoose checks and prepare dependencies
Diagnose a failureFollow symptoms and recovery checks
Investigate missing eventsInspect outbox delivery

Documentation index​

The complete index follows the published sidebar's reading order.

Handbook​

DocumentPurpose
Writing documentationWriting rules, document templates, checks, and publishing
Project conventionsApplication-specific rules and a reference to shared Go conventions
Application profilePurpose, ownership, current capabilities, and documentation gaps
ConfigurationConfiguration sources, backend choices, defaults, and deployment settings
Development workflowSetup, implementation, generation, tooling, and contributions
Testing and verificationSuite selection, test environments, coverage, and checks before review
ArchitectureSource map, component boundaries, request and event flows, and lifecycle
Using the APICredentials, session flow, local verification, and request failure diagnosis
ReleaseVersion selection, release validation, published artifacts, and image identity
DeploymentContainer and Helm configuration, migration handoff, and rollout verification
OperationsProbe checks, process lifecycle, outbox diagnosis, and failure recovery
MonitoringCollect metrics, interpret signals, and configure the supplied dashboard
GitHub configurationRequired and optional workflow variables and secrets

Requirements​

No application requirements are recorded yet. Start with the requirement template.

Decisions​

No application decisions are recorded yet. Start with the decision template.

Templates​

Start new documents from a template and follow the steps for creating a document.

TemplatePurpose
HandbookCurrent behavior, architecture, and working instructions
RequirementDesired outcomes, scope, acceptance criteria, and verification
DecisionSignificant choices, alternatives, reasoning, and consequences

References​

API contracts live with their source definitions. The published site also provides an OpenAPI view.

For the blueprint and its default workflows, see the go42 guide.

See where docs belong when deciding which project to update.


Source: docs/README.md. Revision: 3841815ceb9e.