Public documentation v0
Observability and skill locality
How Software Factory makes work reviewable without leaking internals.
Observable work
The factory prefers streamed progress where possible, structured handoffs, summarized verification evidence, and artifacts that reviewers can inspect without needing private credentials unless explicitly authorized.
Skill locality
pi-sprite runs an agent runtime in one locality while proxying tools to sprite runtime targets. Skill discovery and tool filesystem access can therefore happen in different places. Tasks should explicitly pass required context and declare where execution happens.
Public-safe observability
Public docs describe this as an architectural constraint. Private run directories, raw logs, local paths, secrets, and live operational inventory stay out of the public site.