Docs update - security, issue templates, agentic deployments#15
Merged
Conversation
mkonopelski-gd
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds SECURITY.md and GitHub issue templates for the public repo, fixes broken README links to QUICKSTART.md, and documents the optional agentic deployment and integration-test loop with a worked example spec.
Entrypoint
Start at the new "Agentic Deployment & Integration Tests (Optional)" section in QUICKSTART.md, which ties together the Part F readiness gate, the example spec, and the default GitHub Actions deploy mechanism.
Diagram
N/A — documentation only, no code or workflow changes.
Details
Deploy/E2E readiness (Part F) is deterministic and requires all three of deploy method, test methodology, and infrastructure targets in the spec; partial info keeps a project at LOCAL_ONLY rather than silently defaulting to a live deploy. Agent workspaces have no Docker, kubectl, or cloud CLIs, so any opted-in deploy always runs through a GitHub Actions workflow per backend/app/standards/deployment_standards.md, and SECURITY.md's Design Principles note this happens via Service Account/Workflow Identity Federation with no standing credentials, on cloud infrastructure the user provisions and owns.