Contributing
Read CLAUDE.md and Talos repository specifics. Work on a branch and submit a reviewed pull request when the task authorizes one. Preserve working public Talos interfaces and use one executor for legacy Python, SFD and CLI behavior.
Code of conduct
Our Pledge
Developer documentation
Maintain working model callbacks, reproducible experiment records and portable
Documentation system contract
This page defines the maintained Talos documentation system. It governs source
Documentation style
This page applies the supplied Autonomio website style guide to Talos
Documentation scaffold
docs-site/ assembles the maintained Talos Markdown corpus into a static
Maintenance and executable documentation
Maintain framework compatibility, reproducible records and archive/recovery behavior together. Update supported dependency floors when upstream fixes require it; keep the TensorFlow 2.14 compatibility lane explicit.
Agent entrypoint
Read CLAUDE.md before acting. It is the repository constitution for humans and agents.
Contributor constitution
The repository law, operating discipline, and code stance — the single canonical constitution for every contributor, human or agent.
Governance
Talos is an Autonomio project maintained by Mikko Kotila. Maintainers decide issue priority, product scope, release timing and review outcomes.
Maintainers
Current maintainer: Mikko Kotila (mikkokotila, mailme@mikkokotila.com).
Repository setup
Talos is an existing repository adopting governance tooling. Preserve its package, history, version source, examples and documentation. This runbook configures the external services; it does not recreate or reseed the repository.
PR guideline
Status: canonical universal PR guideline for Autonomio agent work.
Talos repository specifics
This appendix specializes AUTONOMIOPRGUIDELINE.md. The binding laws live in CLAUDE.md.
Configuration
The repository's control surface has two canonical sources. governance.yml describes repository identity, scan paths, gate switches, review authority and policy settings. .github/budgets.json records measured ratchets. Workflows mirror settings that GitHub cannot read from the configuration; contract tests check the mirrors.
Making Release
An authorized maintainer starts the release workflow explicitly. Merging to master does not release Talos.
Packaging
The wheel contains installable Talos runtime files and package-level documentation. The source distribution contains the authored sources needed to inspect, test and build that wheel, including documentation and the adopted repository tooling.
Release Policy
A Talos release publishes a reviewed version of the package with traceable artifacts. Governance adoption does not authorize a release. The operational sequence lives in Making a release.
Security Assurance Case
This page names Talos's trust boundaries and the evidence supporting each adopted control. It distinguishes local tooling from controls that require live activation. SECURITY.md owns private vulnerability reporting.
Semantic Versioning
The version records compatibility of Talos's public Python, CLI, configuration, manifest and artifact contracts.
Technical Debt
Record accepted limitations with their evidence and repair condition. Work not yet started belongs in an issue. The register below describes existing constraints; it does not claim they are harmless.
Writing Docstrings
A docstring earns its place by stating a constraint, unit, return meaning, side effect or failure boundary that the signature does not express. The adopted gates check form and measured debt; reviewers check meaning.
OpenSSF evidence
Talos has an OpenSSF Best Practices application