Skip to content

Commit 67484c4

Browse files
committed
Added start docs.
1 parent deb9707 commit 67484c4

17 files changed

Lines changed: 108 additions & 177 deletions

docs/capabilities/Execution.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,3 +16,13 @@ gemara:
1616
## Description
1717

1818
Execution capability allows agents to run the code they generate or invoke, observe outputs, and iterate based on results. This enables autonomous debugging, testing, and deployment workflows.
19+
20+
## Privileged Execution
21+
22+
A critical aspect of agent execution is that it typically occurs **on behalf of the user**, inheriting their credentials, permissions, and access rights. This means:
23+
24+
- **Ambient Authority**: Agents execute with whatever permissions the user has granted to the development environment — often broad access to filesystems, networks, cloud resources, and secrets.
25+
- **Credential Inheritance**: API keys, SSH keys, cloud credentials, and other secrets accessible to the user become accessible to the agent.
26+
- **Impersonation**: Actions taken by the agent may be indistinguishable from actions taken by the user in audit logs and access control systems.
27+
28+
This creates an amplification effect: a compromised or misdirected agent can cause harm proportional to the user's privilege level, not the agent's intended scope.

docs/capabilities/Start.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
title: Agentic Software Development Capabilities
3+
description: The foundational capabilities that enable AI agents to participate in software development
4+
sidebar_position: 1
5+
slug: /capabilities
6+
---
7+
8+
# Agentic Capabilities
9+
10+
The capabilities that enable AI agents to autonomously participate in software development workflows. Each capability represents a distinct type of action an agent can take — and each introduces its own threat surface.
11+
12+
## Why Capabilities Matter
13+
14+
Understanding capabilities is essential for risk management because:
15+
16+
- **Capabilities enable threats**: Every risk in this framework is enabled by one or more capabilities. You cannot have "supply chain poisoning" without `internet-access`; you cannot have "verification illusion" without `code-generation`.
17+
- **Capabilities can be constrained**: The most direct control over agent risk is limiting which capabilities an agent has access to.
18+
- **Capabilities compound**: Agents with multiple capabilities can chain them in unexpected ways — `file-system-access` + `internet-access` = data exfiltration potential.
19+
20+
## Capability Inventory
21+
22+
<TagList tag="Capability" filter="capabilities" />

docs/capabilities/_category_.yaml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
11
---
22
label: Capabilities
3+
link:
4+
id: Start
5+
type: doc
36
position: 1

docs/practices/Independent-Verification.md

Lines changed: 0 additions & 96 deletions
This file was deleted.

docs/practices/Start.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Agentic Software Development Practices
3+
description: Controls and practices for managing risks in agentic software development
4+
sidebar_position: 1
5+
slug: /practices
6+
---
7+
8+
# Agentic Practices
9+
10+
Controls, practices, and mitigations for managing the risks introduced by AI agents in software development workflows.
11+
12+
## Practice Inventory
13+
14+
<TagList tag="Control" filter="practices" />

docs/practices/_category_.yaml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,6 @@
11
---
22
label: Practices / Controls
3+
link:
4+
id: Start
5+
type: doc
36
position: 3

docs/risks/Autonomy-Control-Risks.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,9 @@ gemara:
2626
- name: AI Agent
2727
type: Internal
2828
description: Pursues goals that diverge from human intent, optimizes proxy metrics, or self-modifies constraints
29+
- name: Human Operator
30+
type: Internal
31+
description: Grants excessive autonomy, fails to set appropriate boundaries, or does not intervene when agent exceeds scope
2932
external-mappings:
3033
- reference-id: mitre-atlas
3134
entries:

docs/risks/Containment-Isolation-Risks.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,9 @@ gemara:
2626
- name: AI Agent
2727
type: Internal
2828
description: Discovers and exploits containment weaknesses through normal operation or tool chaining
29+
- name: Human Operator
30+
type: Internal
31+
description: Configures weak containment, grants excessive permissions, or disables safeguards for convenience
2932
external-mappings:
3033
- reference-id: mitre-atlas
3134
entries:

docs/risks/Data-Privacy-Risks.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ tags:
88
gemara:
99
id: data-privacy-risks
1010
title: Data & Privacy Risks
11-
description: Threats arising from AI agents that expose secrets in code, leak sensitive data through network access, retain PII inappropriately, or violate data handling policies.
11+
description: Threats arising from AI agents that expose secrets in code, leak sensitive data through network access, retain or leak PII inappropriately, or violate data handling policies.
1212
capabilities:
1313
- reference-id: file-system-access
1414
entries:
@@ -29,6 +29,9 @@ gemara:
2929
- name: AI Agent
3030
type: Internal
3131
description: Handles sensitive data without appropriate care, embeds secrets in code, or retains PII inappropriately
32+
- name: Human Operator
33+
type: Internal
34+
description: Grants agent excessive data access, fails to configure data handling boundaries, or shares secrets in prompts
3235
external-mappings:
3336
- reference-id: mitre-atlas
3437
entries:

docs/risks/Deployment-Rollback-Risks.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,9 @@ gemara:
2626
- name: AI Agent
2727
type: Internal
2828
description: Prioritizes deployment speed over safety, creates irreversible states, or bypasses approval gates
29+
- name: Human Operator
30+
type: Internal
31+
description: Approves risky deployments without adequate review, sets weak approval gates, or skips rollback planning
2932
external-mappings:
3033
- reference-id: mitre-atlas
3134
entries:

0 commit comments

Comments
 (0)