docs(glossary): add Agent, Operator, Service; split "exposed" #19
No reviewers
Labels
No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wontfix
needs-info
needs-triage
ready-for-agent
ready-for-human
review/merge-ready
review/needs-fix
review/needs-human
review/needs-review
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
olympus/infra-forge!19
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/glossary-exposure-and-agent-terms"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds four terms the forgejo-mcp grilling surfaced, and fixes one overloaded word.
## Peoplesection):docs/agents/anddocs/agents/domain.mduse both words throughout without ever defining them.Structure): a program an Ansible role installs on a Guest and runs under systemd. Forgejo and the Actions runner are already two; the distinction was implicit in the architecture page only.## Exposuresection): "exposed" was being asked to mean both at once. The pair keeps the Edge's WAN-only definition intact and makes the exposure decision explicit.Definitions only — no implementation detail, per the glossary's own rule.
Context: this vocabulary is what the forgejo-mcp spec (#17) is written in.