Add FAQ to docs/topics#20
Open
bar-capsule wants to merge 3 commits into
Open
Conversation
Adds a new documentation page covering ACS positioning, scope, paradigm support, deployment, operations, and roadmap. Content is sourced from the merged v0.1.0 spec; no normative claims beyond what conformance.md defines. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Two new questions under About ACS: - What is a hook? (with airport-security analogy) - How does it all combine in one session? (four-step walkthrough of handshake -> action -> audit -> seal) Both written in simple language, no spec internals or jargon. The hook question gives a reader the building block; the session question shows how the three pillars combine in one runtime story. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
afogel
previously approved these changes
Jun 15, 2026
PR Agent-Control-Standard#21 promotes subagentStart and subagentStop from SHOULD to MUST in the ACS-Core hook minimum (8 hooks instead of 6). Update the FAQ to match: - "How do I make my framework ACS-conformant?" lists subagent hooks in the mandatory floor with a short justification. - "What if my framework does not have a particular hook surface?" no longer lists subagent hooks under "Additional hooks (SHOULD)"; they are now part of Core. Frameworks without a sub-agent abstraction satisfy this requirement vacuously, which is the same shape as the merged spec's "implement when observable" pattern. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
|
Merge-order note: hold this until #21 lands, and reconcile the FAQ to the slimmed floor before merging. Right now
Fix is small: update those FAQ lines to match #21's floor, then merge after #21. No git conflict with #21 (different files), so this is sequencing for consistency, not a rebase. cc @afogel since you approved this. The catch before merge is the FAQ reconcile plus ordering after #21. @bar-capsule |
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
3 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 a new documentation page (
docs/topics/faq.md) covering ACS positioning, scope, paradigm support, deployment, operations, and roadmap.The FAQ answers questions from four audiences (enterprise security teams, framework implementers, researchers, press) on one page, sourced from the merged v0.1.0 spec. No normative claims beyond what
docs/spec/conformance.mddefines.What lands
docs/topics/faq.md— new file, ~25 Q&As across six sections (About ACS / Scope and boundaries / For framework implementers / For enterprises / For researchers and paradigm authors / Versioning and roadmap)mkdocs.yml— one-line nav addition adding the FAQ under the existingTopicsgroupTest plan
mkdocs serverenders the new page under Topics → FAQ🤖 Generated with Claude Code