Some checks failed
		
		
	
	Docs CI / lint-and-preview (push) Has been cancelled
				
			- Introduced guild charters for Scanner Deno, PHP, Ruby, Native, WebService, Java, Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, UI, Zastava Observer, Zastava Webhook, Zastava Core, and Plugin Platform. - Each charter outlines the mission, scope, required reading, and working agreements for the respective guilds. - Created task boards for Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, and Zastava components to track progress and dependencies. - Ensured all documents emphasize determinism, offline readiness, security, and integration with shared Surface libraries.
		
			
				
	
	
		
			23 lines
		
	
	
		
			1.2 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
			
		
		
	
	
			23 lines
		
	
	
		
			1.2 KiB
		
	
	
	
		
			Markdown
		
	
	
	
	
	
# DevOps & Release — Agent Charter
 | 
						|
 | 
						|
## Mission
 | 
						|
Execute deterministic build/release pipeline per `docs/modules/devops/ARCHITECTURE.md`:
 | 
						|
- Reproducible builds with SBOM/provenance, cosign signing, transparency logging.
 | 
						|
- Channel manifests (LTS/Stable/Edge) with digests, Helm/Compose profiles.
 | 
						|
- Performance guard jobs ensuring budgets.
 | 
						|
 | 
						|
## Expectations
 | 
						|
- Coordinate with Scanner/Scheduler/Notify teams for artifact availability.
 | 
						|
- Maintain CI reliability; update `TASKS.md` as states change.
 | 
						|
 | 
						|
## Required Reading
 | 
						|
- `docs/modules/platform/architecture-overview.md`
 | 
						|
- `docs/modules/airgap/airgap-mode.md`
 | 
						|
 | 
						|
## Working Agreement
 | 
						|
- 1. Update task status to `DOING`/`DONE` in both `docs/implplan/SPRINTS.md` and the local `TASKS.md` when you start or finish work.
 | 
						|
- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
 | 
						|
- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
 | 
						|
- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
 | 
						|
- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.
 |