Skip to main content

ATS Schema Reference

ATS.manifest.toml​

The standard manifest. Describes ATS itself: identity, governance relationships, artifact locations, and lifecycle.

[standard]
id = "ats"
title = "Agent Task Standard"
abbreviation = "ATS"
status = "active"
maturity = "candidate"
version = "0.2.1"
description = "Governs agent task records, lifecycle states, context capture, handoff, validation records, and replayability."

[governance]
meta_standard = "SFDS"
workspace_standard = "WGS"
scope = "Agent workflows, task records, context capture, validation summaries, blockers, handoffs, and replayability."
non_goals = ["Workspace root layout", "project proposal criteria", "release packaging"]

[artifacts]
specification = "Agent Task Standard.md"
schema = "AgentTaskRecord.schema.toml"
templates = "templates"
examples = "examples"
adoption_guide = "Adoption-Guide.md"
validation_checklist = "Validation-Checklist.md"
changelog = "CHANGELOG.md"
validators = []
governance_notes = []
reference_examples = [
  "examples/ATS-Suite-Map.md",
  "examples/Completed-Agent-Task-Record.md",
  "examples/Blocked-Handoff-Note.md"
]

[adopter_artifacts]
schemas = ["AgentTaskRecord.schema.toml"]
manifest_templates = []
document_templates = [
  "templates/Agent-Task-Record.md",
  "templates/Handoff-Note.md"
]

[lifecycle]
created = "2026-06-10"
last_updated = "2026-06-11"
maintainer = "Herb"

[agent]
read_first = ["README.md", "Agent Task Standard.md", "ATS.manifest.toml"]
notes = "Use ATS after WGS orientation to record substantial agent work, handoffs, validation, blockers, and replayable context."
  • [standard] — identity block: id, title, abbreviation, status, maturity, version, one-line description.
  • [governance] — links to SFDS (meta-standard) and WGS (workspace standard), states scope and non-goals.
  • [artifacts] — points to the specification, schema, templates/examples folders, adoption guide, validation checklist, changelog.
  • [adopter_artifacts] — the task record and handoff note templates that agents actually fill in; ATS has no manifest templates of its own since it records task history rather than project metadata.
  • [lifecycle] — creation/update dates and maintainer.
  • [agent] — reading order for agents onboarding onto ATS; notes it applies after WGS orientation.

AgentTaskRecord.schema.toml​

The schema that validates an Agent-Task-Record.md (or a machine-readable equivalent).

title = "Agent Task Record Schema"
type = "object"
required = ["goal", "starting_context", "governing_standards", "actions_taken", "validation", "remaining_work"]

[properties.goal]
type = "string"
required = true

[properties.starting_context]
required = ["workspace", "relevant_files", "prior_state"]

[properties.governing_standards]
type = "array"

[properties.actions_taken]
type = "array"

[properties.validation]
required = ["commands_or_checks", "result", "evidence"]

[properties.remaining_work]
type = "array"

[properties.known_risks]
type = "array"
  • goal — required string describing what the task set out to accomplish.
  • starting_context — required workspace path, relevant files, and prior state, so a resuming agent isn't guessing at what was already known.
  • governing_standards — array of standards the task was executed under.
  • actions_taken — array summarizing files inspected/changed, commands run, and decisions made.
  • validation — required checks performed, result, and supporting evidence.
  • remaining_work / known_risks — arrays capturing open work and risk notes for the next agent.