Skip to main content

SIS Schema Reference

SIS.manifest.toml​

The standard manifest for SIS itself.

[standard]
id = "sis"
title = "Service and Infrastructure Standard"
abbreviation = "SIS"
status = "active"
maturity = "candidate"
version = "0.1.0"
description = "Governs local-first services, daemons, local APIs, shared infrastructure, lifecycle commands, health checks, ports, logs, state paths, resource bounds, and recovery procedures."

[governance]
meta_standard = "SFDS"
workspace_standard = "WGS"
scope = "Long-running local services, shared infrastructure, background daemons, local APIs, cache services, model services, schedulers, health checks, lifecycle controls, and resource contracts."
non_goals = ["Desktop release packaging", "one-shot CLI command output", "website deployment", "dataset provenance"]

[artifacts]
specification = "Service and Infrastructure Standard.md"
schema = "ServiceManifest.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/SIS-Suite-Map.md",
  "examples/Example-Local-API-Service.md",
  "examples/Example-Workspace-Cache-Service.md"
]

[adopter_artifacts]
schemas = ["ServiceManifest.schema.toml"]
manifest_templates = ["templates/Service-Manifest.toml"]
document_templates = [
  "templates/Service-Runbook.md",
  "templates/Health-Check-Contract.md",
  "templates/Resource-Constraint-Contract.md"
]

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

[agent]
read_first = ["README.md", "Service and Infrastructure Standard.md", "SIS.manifest.toml"]
notes = "Use SIS for local-first background services, shared infrastructure, daemons, local APIs, caches, model services, schedulers, and any project class that runs beyond a one-shot command."
  • [standard] identifies SIS at candidate maturity, v0.1.0 — the youngest of the four standards in this batch.
  • [governance] records the meta-standard (SFDS), workspace standard (WGS), scope, and non-goals.
  • [artifacts] indexes the specification, schema, templates, examples, and reference examples (a local API service and a workspace cache service).
  • [adopter_artifacts] lists what a service adopting SIS uses: the manifest schema, the manifest template, and three document templates (runbook, health check contract, resource constraint contract).

ServiceManifest.schema.toml​

The service manifest schema — every SIS-governed service's manifest should satisfy this shape. Eight top-level sections are all required: service, governance, lifecycle, health, network, storage, resources, operations.

title = "SIS Service Manifest Schema"
type = "object"
required = ["service", "governance", "lifecycle", "health", "network", "storage", "resources", "operations"]

[properties.service]
required = ["id", "title", "class", "readiness"]

[properties.governance]
required = ["standard", "workspace_standard", "proposal_standard"]

[properties.lifecycle]
required = ["start", "stop", "restart", "status"]

[properties.health]
required = ["mode", "contract", "statuses"]

[properties.network]
required = ["ports", "bind_policy"]

[properties.storage]
required = ["state_paths", "cache_paths", "log_paths"]

[properties.resources]
required = ["log_rotation", "cache_limit", "cleanup"]

[properties.operations]
required = ["runbook", "recovery", "agent_rules"]
  • service — identity: id, title, class (service or infrastructure), readiness level.
  • governance — which standards govern the service: SIS itself, the workspace standard (WGS), and the proposal standard (PPS).
  • lifecycle — the four required lifecycle commands (start, stop, restart, status).
  • health — the health check mode, its contract document, and the set of valid status values.
  • network — port declarations and the bind policy (e.g. local-only).
  • storage — state, cache, and log path declarations.
  • resources — log rotation policy, cache limit, and cleanup behavior.
  • operations — the runbook document, recovery procedure, and agent-safe operating rules.

See templates/Service-Manifest.toml (in Templates) for a fully annotated, fillable version, and the Local API and Workspace Cache examples for filled instances.