Project Repositories Acceptance Criteria

acceptance criterion · created

Evidence record

What is verified
Uses in published workflows: 0
Source
Published workflow connections
Revision
Version 0.1.3
Validation status
Public-sanitized publication; no independent validation is claimed.

What this is and why

Acceptance criteria for the three project repositories and the sanitization gate. The public showcase repository must be public and carry the sanitized-trace disclaimer; the site and backend repositories must be private, verified via the organization listing. The sanitization policy must exist both as a document and as a blocking check on every push and pull request, mutation-proven with a planted internal address, and the secret scanner must detect planted positive controls on every run. A gate never seen red is not evidence.

Where it was applied and what it helped deliver

No published workflow records this capability yet — the count includes only ledger mentions that resolve.

Relations

Neighbor diagram: this capability’s direct relations in the knowledge graph part-of uses uses repo-provisioning-sanitiz… sanitized-projection sanitization-gate Project Repositories Acceptan…
Uses: part-of
repo-provisioning-sanitized
Uses: uses
sanitized-projectionsanitization-gate

Show this capability and its neighbours in the catalog

Metadata and provenance

id
tal-sc-stage-1-repos
type
acceptance criterion
version
0.1.3
origin
created in Talomnia
lifecycle
public_sanitized
tags
repos, tz-4, tz-3-3, tz-14-8

The source is the private knowledge repository; only the sanitized public projection reaches this site.

verified · tal-sc-stage-1-repos · v0.1.3