@bluefly/openstandardagents 0.3.2 → 0.3.3

package/dist/spec/v0.3.3/access_tiers.yaml

@@ -0,0 +1,375 @@
+# =============================================================================
+# OSSA v0.3.3 - Access Tiers & Separation of Duties Specification
+# =============================================================================
+# Defines privilege levels, role separations, and access controls for agents
+# Issue: https://gitlab.com/blueflyio/openstandardagents/-/issues/363
+# =============================================================================
+
+apiVersion: ossa/v0.3.3
+kind: AccessTierSpec
+version: "1.0.0"
+
+# =============================================================================
+# ACCESS TIERS
+# Hierarchical privilege levels - every agent must declare exactly one tier
+# Lower tier number = more restricted permissions
+# =============================================================================
+tiers:
+  tier_1_read:
+    name: "Read Only (Analyzers)"
+    level: 1
+    description: "Agents that analyze, audit, scan - cannot modify state"
+    permissions:
+      - read_code
+      - read_configs
+      - read_metrics
+      - read_logs
+      - read_issues
+      - read_mrs
+      - execute_queries  # Read-only queries
+    prohibited:
+      - write_*
+      - delete_*
+      - execute_commands
+      - modify_infrastructure
+    typical_roles:
+      - analyzer
+      - auditor
+      - scanner
+      - reviewer
+      - monitor
+    examples:
+      - security-scanner
+      - code-analyzer
+      - compliance-auditor
+      - cost-reporter
+      - health-monitor
+    requires_approval: false
+    audit_level: standard
+
+  tier_2_write_limited:
+    name: "Write Limited (Workers)"
+    level: 2
+    description: "Agents that create/modify in sandboxed areas only"
+    permissions:
+      - read_*
+      - write_docs
+      - write_tests
+      - write_scaffolds
+      - write_configs_draft
+      - create_issues
+      - create_mrs_draft
+      - execute_sandboxed
+    prohibited:
+      - write_production_code
+      - merge_mrs
+      - delete_branches
+      - modify_infrastructure
+      - modify_secrets
+    typical_roles:
+      - generator
+      - scaffolder
+      - documenter
+      - test_writer
+    examples:
+      - doc-generator
+      - test-generator
+      - module-scaffolder
+      - changelog-generator
+    requires_approval: false
+    audit_level: standard
+
+  tier_3_write_elevated:
+    name: "Write Elevated (Operators)"
+    level: 3
+    description: "Agents that modify production systems with approval chains"
+    permissions:
+      - read_*
+      - write_*
+      - execute_deployments
+      - modify_pipelines
+      - merge_mrs  # With approval
+      - modify_configs
+      - execute_commands  # Non-destructive
+    prohibited:
+      - delete_production
+      - modify_secrets_direct
+      - bypass_approvals
+      - force_push
+    typical_roles:
+      - deployer
+      - operator
+      - executor
+      - maintainer
+    examples:
+      - deployment-agent
+      - gitlab-cicd-agent
+      - incident-responder
+      - infrastructure-operator
+    requires_approval: true
+    approval_chain:
+      - type: human_or_governor
+        timeout_minutes: 30
+    audit_level: detailed
+
+  tier_4_policy:
+    name: "Policy (Governors)"
+    level: 4
+    description: "Agents that define and enforce policies - ISOLATED from execution"
+    permissions:
+      - read_*
+      - define_policies
+      - publish_policies
+      - audit_compliance
+      - report_violations
+    prohibited:
+      - execute_*
+      - write_code
+      - modify_infrastructure
+      - remediate_direct  # Must delegate to Tier 3
+    typical_roles:
+      - governor
+      - policy_definer
+      - compliance_officer
+    examples:
+      - compliance-policy-engine
+      - security-policy-manager
+      - cost-governance-agent
+    requires_approval: false
+    isolation: strict
+    audit_level: comprehensive
+
+# =============================================================================
+# ROLE SEPARATION RULES
+# Defines which roles can coexist and which must be separated
+# =============================================================================
+separation_rules:
+  # Critics cannot execute
+  critic_executor_separation:
+    name: "Critic-Executor Separation"
+    description: "Agents that review/critique cannot also approve/execute"
+    conflicting_roles:
+      - [reviewer, approver]
+      - [critic, executor]
+      - [auditor, remediator]
+    enforcement: strict
+    rationale: "Prevents conflict of interest in quality gates"
+
+  # Governors cannot execute
+  governor_executor_separation:
+    name: "Governor-Executor Separation"
+    description: "Policy-defining agents cannot execute policies"
+    conflicting_roles:
+      - [policy_definer, enforcer]
+      - [governor, operator]
+      - [rule_maker, rule_executor]
+    enforcement: strict
+    rationale: "Separation of legislative and executive functions"
+
+  # Readers and writers should be separate for sensitive domains
+  read_write_separation:
+    name: "Read-Write Separation (Sensitive)"
+    description: "In security/compliance domains, readers cannot write"
+    applies_to_domains:
+      - security
+      - compliance
+      - secrets
+    conflicting_roles:
+      - [reader, writer]
+      - [scanner, remediator]
+    enforcement: recommended
+    exceptions:
+      - domain: development
+        reason: "Dev workflows need read-write for productivity"
+
+  # Production isolation
+  production_isolation:
+    name: "Production Isolation"
+    description: "Agents modifying production must have explicit elevation"
+    environments:
+      - production
+      - staging  # Optional
+    required_tier: tier_3_write_elevated
+    enforcement: strict
+    rationale: "Production changes require elevated privileges and audit"
+
+# =============================================================================
+# APPROVAL CHAINS
+# Defines approval workflows for privileged operations
+# =============================================================================
+approval_chains:
+  standard:
+    name: "Standard Approval"
+    description: "Single human or governor approval"
+    steps:
+      - type: human_or_governor
+        required: 1
+        timeout_minutes: 60
+
+  elevated:
+    name: "Elevated Approval"
+    description: "Human approval required for critical operations"
+    steps:
+      - type: governor
+        required: 1
+        timeout_minutes: 15
+      - type: human
+        required: 1
+        timeout_minutes: 120
+
+  critical:
+    name: "Critical Approval"
+    description: "Multi-party approval for production changes"
+    steps:
+      - type: automated_checks
+        required: all
+        checks:
+          - security_scan
+          - compliance_check
+          - rollback_plan_exists
+      - type: governor
+        required: 1
+        timeout_minutes: 15
+      - type: human
+        required: 2  # Two human approvers
+        timeout_minutes: 240
+
+# =============================================================================
+# DELEGATION RULES
+# How higher-tier agents can delegate to lower-tier agents
+# =============================================================================
+delegation:
+  rules:
+    # Tier 4 can delegate enforcement to Tier 3
+    - from_tier: tier_4_policy
+      to_tier: tier_3_write_elevated
+      operations:
+        - remediate_violations
+        - apply_policies
+      requires:
+        - delegation_token
+        - audit_trail
+        - violation_report
+
+    # Tier 3 can delegate read operations to Tier 1
+    - from_tier: tier_3_write_elevated
+      to_tier: tier_1_read
+      operations:
+        - gather_information
+        - run_analysis
+        - generate_reports
+      requires:
+        - task_specification
+
+    # Tier 2 can delegate read operations to Tier 1
+    - from_tier: tier_2_write_limited
+      to_tier: tier_1_read
+      operations:
+        - analyze_code
+        - scan_dependencies
+      requires:
+        - task_specification
+
+  prohibited_delegations:
+    # Lower tiers cannot elevate themselves
+    - from: [tier_1_read, tier_2_write_limited]
+      to: [tier_3_write_elevated, tier_4_policy]
+      reason: "Privilege escalation not permitted"
+
+    # Governors cannot delegate policy definition
+    - from: tier_4_policy
+      operation: define_policies
+      reason: "Policy definition cannot be delegated"
+
+# =============================================================================
+# AUDIT REQUIREMENTS BY TIER
+# =============================================================================
+audit:
+  standard:
+    retention_days: 30
+    includes:
+      - agent_id
+      - operation
+      - timestamp
+      - result
+
+  detailed:
+    retention_days: 90
+    includes:
+      - agent_id
+      - operation
+      - timestamp
+      - result
+      - input_summary
+      - affected_resources
+      - approval_chain
+
+  comprehensive:
+    retention_days: 365
+    includes:
+      - agent_id
+      - operation
+      - timestamp
+      - result
+      - full_input
+      - full_output
+      - affected_resources
+      - approval_chain
+      - policy_version
+      - compliance_status
+
+# =============================================================================
+# USAGE IN AGENT MANIFESTS
+# =============================================================================
+# Example usage in OSSA agent manifest:
+#
+# metadata:
+#   name: security-scanner
+#   labels:
+#     access_tier: tier_1_read
+#
+# spec:
+#   access:
+#     tier: tier_1_read
+#     permissions:
+#       - read_code
+#       - read_configs
+#       - execute_queries
+#     prohibited:
+#       - write_*
+#     audit_level: standard
+#
+#   separation:
+#     role: analyzer
+#     conflicts_with:
+#       - executor
+#       - remediator
+#
+# =============================================================================
+# VALIDATION RULES
+# =============================================================================
+validation:
+  rules:
+    - name: valid-tier
+      description: "Access tier must be from approved list"
+      severity: error
+
+    - name: role-separation
+      description: "Conflicting roles must not coexist"
+      severity: error
+
+    - name: tier-permission-match
+      description: "Permissions must be allowed by tier"
+      severity: error
+
+    - name: prohibited-operations
+      description: "Prohibited operations must not be declared"
+      severity: error
+
+    - name: approval-chain-required
+      description: "Elevated tiers require approval chains"
+      severity: warning
+
+    - name: delegation-valid
+      description: "Delegations must follow rules"
+      severity: error

package/{spec/v0.3.0 → dist/spec/v0.3.3}/adapters/drupal.md

@@ -100,7 +100,7 @@ ECA (Event-Condition-Action) rules map naturally to OSSA Tasks with event trigge
 
 ```yaml
 # ECA Model → OSSA Task
-apiVersion: ossa/v0.3.0
+apiVersion: ossa/v0.3.3
 kind: Task
 metadata:
   name: eca-node-publish
@@ -156,7 +156,7 @@ runtime:
 
 ```yaml
 # Maestro Template → OSSA Workflow
-apiVersion: ossa/v0.3.0
+apiVersion: ossa/v0.3.3
 kind: Workflow
 metadata:
   name: content-approval-workflow
@@ -226,7 +226,7 @@ runtime:
 
 ```yaml
 # FlowDrop Diagram → OSSA Workflow
-apiVersion: ossa/v0.3.0
+apiVersion: ossa/v0.3.3
 kind: Workflow
 metadata:
   name: user-registration-flow
@@ -299,7 +299,7 @@ runtime:
 
 ```yaml
 # AI Agent Runner → OSSA Agent
-apiVersion: ossa/v0.3.0
+apiVersion: ossa/v0.3.3
 kind: Agent
 metadata:
   name: content-assistant
@@ -348,7 +348,7 @@ runtime:
 
 ```yaml
 # Minikanban Card → OSSA Task
-apiVersion: ossa/v0.3.0
+apiVersion: ossa/v0.3.3
 kind: Task
 metadata:
   name: kanban-task
@@ -523,7 +523,7 @@ spec:
 
 ## OSSA Compliance
 
-This adapter implements OSSA v0.3.0 specification:
+This adapter implements OSSA v0.3.3 specification:
 
 - ✅ Task execution with deterministic semantics
 - ✅ Workflow orchestration with step dependencies
@@ -535,7 +535,7 @@ This adapter implements OSSA v0.3.0 specification:
 
 ## Related
 
-- [OSSA Specification v0.3.0](../README.md)
+- [OSSA Specification v0.3.3](../README.md)
 - [Symfony Adapter](./symfony.md)
 - [Node.js Adapter](./nodejs.md)
 - [Capability Registry](../capability-schema.md)

package/dist/spec/{v0.3.0 → v0.3.3}/adapters/symfony.md

@@ -350,7 +350,7 @@ ossa:
 
 ```yaml
 # config/ossa/tasks/send-email.yaml
-apiVersion: ossa/v0.3.0
+apiVersion: ossa/v0.3.3
 kind: Task
 metadata:
   name: send-email-symfony
@@ -419,7 +419,7 @@ runtime:
 
 ```yaml
 # config/ossa/workflows/user-onboarding.yaml
-apiVersion: ossa/v0.3.0
+apiVersion: ossa/v0.3.3
 kind: Workflow
 metadata:
   name: user-onboarding-symfony
@@ -640,7 +640,7 @@ php bin/console messenger:failed:retry --all
 
 ## OSSA Compliance
 
-This adapter implements OSSA v0.3.0 specification:
+This adapter implements OSSA v0.3.3 specification:
 
 - ✅ Task execution with deterministic semantics
 - ✅ Workflow orchestration with step dependencies
@@ -653,7 +653,7 @@ This adapter implements OSSA v0.3.0 specification:
 
 ## Related
 
-- [OSSA Specification v0.3.0](../README.md)
+- [OSSA Specification v0.3.3](../README.md)
 - [Drupal Adapter](./drupal.md)
 - [Node.js Adapter](./nodejs.md)
 - [Capability Registry](../capability-schema.md)

package/{spec/v0.3.0 → dist/spec/v0.3.3}/agent-test.schema.json

@@ -1,6 +1,6 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
-  "$id": "https://openstandardagents.org/schemas/v0.3.0/agent-test.json",
+  "$id": "https://openstandardagents.org/schemas/v0.3.3/agent-test.json",
   "title": "OSSA AgentTest Resource",
   "description": "Test definition for OSSA agents - declarative testing framework for agent behavior, performance, and compliance validation",
   "type": "object",
@@ -13,7 +13,7 @@
   "properties": {
     "apiVersion": {
       "type": "string",
-      "const": "ossa/v0.3.0",
+      "const": "ossa/v0.3.3",
       "description": "OSSA API version for AgentTest resources"
     },
     "kind": {

package/dist/spec/v0.3.3/examples/access-tiers/README.md

@@ -0,0 +1,106 @@
+# OSSA v0.3.3 Access Tiers Examples
+
+This directory contains example agent manifests demonstrating the **Access Tiers** and **Separation of Duties** features introduced in OSSA v0.3.3.
+
+## Access Tier Hierarchy
+
+| Tier | Name | Description | Example Agents |
+|------|------|-------------|----------------|
+| `tier_1_read` | Read Only (Analyzers) | Cannot modify state | Scanners, Reviewers, Monitors |
+| `tier_2_write_limited` | Write Limited (Workers) | Sandboxed writes only | Doc generators, Test writers |
+| `tier_3_write_elevated` | Write Elevated (Operators) | Production access with approval | Deployers, Infrastructure operators |
+| `tier_4_policy` | Policy (Governors) | Defines policies, CANNOT execute | Compliance governors |
+
+## Examples
+
+### Tier 1: Read Only
+- **[security-scanner.ossa.yaml](./security-scanner.ossa.yaml)** - Vulnerability scanner that cannot remediate
+- **[code-critic.ossa.yaml](./code-critic.ossa.yaml)** - Code reviewer that cannot approve
+
+### Tier 2: Write Limited
+- **[doc-generator.ossa.yaml](./doc-generator.ossa.yaml)** - Documentation generator with sandboxed access
+
+### Tier 3: Write Elevated
+- **[deployment-operator.ossa.yaml](./deployment-operator.ossa.yaml)** - Deployment agent with approval chains
+
+### Tier 4: Policy
+- **[compliance-governor.ossa.yaml](./compliance-governor.ossa.yaml)** - Policy definer that cannot execute
+
+## Key Separation Rules
+
+### Critic-Executor Separation
+Agents that review/critique **cannot** also approve/execute:
+- Reviewers cannot approve MRs
+- Auditors cannot remediate findings
+- Critics cannot merge changes
+
+### Governor-Executor Separation
+Policy-defining agents **cannot** execute policies:
+- Governors define rules, operators enforce them
+- Policy definers cannot modify infrastructure
+- Compliance agents cannot remediate directly
+
+### Read-Write Separation (Sensitive Domains)
+In security/compliance domains, readers should not write:
+- Scanners cannot remediate
+- Auditors cannot fix violations
+- Monitors cannot modify configurations
+
+## Usage in Agent Manifests
+
+```yaml
+apiVersion: ossa/v0.3.3
+kind: Agent
+
+metadata:
+  name: my-agent
+  labels:
+    access_tier: tier_1_read  # Label for filtering
+
+spec:
+  type: analyzer  # Agent type aligned with tiers
+
+  # Taxonomy classification
+  taxonomy:
+    domain: security
+    subdomain: vulnerability
+    capability: scan_code
+    concerns:
+      - quality
+      - governance
+
+  # Access tier configuration
+  access:
+    tier: tier_1_read
+    permissions:
+      - read_code
+      - read_configs
+    prohibited:
+      - write_*
+    audit_level: standard
+
+  # Role separation
+  separation:
+    role: scanner
+    conflicts_with:
+      - remediator
+      - executor
+    prohibited_actions:
+      - execute
+      - merge
+```
+
+## Validation
+
+Use the OSSA CLI to validate access tier compliance:
+
+```bash
+ossa validate manifest.yaml --check-separation
+ossa audit --tier-violations
+```
+
+## Related Specifications
+
+- [access_tiers.yaml](../../access_tiers.yaml) - Full access tier definitions
+- [taxonomy.yaml](../../taxonomy.yaml) - Domain taxonomy with tier mappings
+- [ossa-0.3.3.schema.json](../../ossa-0.3.3.schema.json) - JSON Schema with tier validation

package/dist/spec/v0.3.3/examples/access-tiers/code-critic.ossa.yaml

@@ -0,0 +1,105 @@
+apiVersion: ossa/v0.3.3
+kind: Agent
+metadata:
+  name: code-critic
+  version: 1.0.0
+  description: Code review critic - provides feedback, cannot approve
+  labels:
+    team: platform
+    access_tier: tier_1_read
+    domain: development
+  annotations:
+    ossa.io/migration: v0.3.3-to-v0.3.3
+    ossa.io/migrated-date: 2026-01-07
+spec:
+  type: critic
+  role: |
+    You are a code review critic that analyzes merge requests and provides
+    detailed feedback on code quality, architecture, and best practices.
+
+    CRITICAL SEPARATION RULE:
+    - You CANNOT approve merge requests
+    - You CANNOT merge changes
+    - You CANNOT execute code modifications
+    - You can ONLY provide feedback and recommendations
+
+    Your role is to critique, not to approve. Approvals must come from
+    human reviewers or designated approver agents (which you cannot be).
+  llm:
+    provider: anthropic
+    model: claude-sonnet-4-20250514
+    temperature: 0.2
+  taxonomy:
+    domain: development
+    subdomain: code-review
+    capability: review_code
+    concerns:
+      - quality
+      - architecture
+  access:
+    tier: tier_1_read
+    permissions:
+      - read_code
+      - read_configs
+      - read_mrs
+      - read_issues
+      - execute_queries
+    prohibited:
+      - write_*
+      - merge_mrs
+      - approve
+    audit_level: standard
+    requires_approval: false
+  separation:
+    role: critic
+    conflicts_with:
+      - approver
+      - executor
+      - merger
+    prohibited_actions:
+      - approve
+      - merge
+      - execute
+  tools:
+    - name: gitlab-mr-reader
+      type: api
+      config:
+        endpoint: https://gitlab.com/api/v4
+        methods:
+          - GET
+        scopes:
+          - read_api
+    - name: code-analyzer
+      type: mcp
+      config:
+        server: code-analysis-mcp-server
+  autonomy:
+    level: semi_autonomous
+    allowed_actions:
+      - read_code
+      - analyze_mr
+      - post_comment
+      - request_changes
+    blocked_actions:
+      - approve_mr
+      - merge_mr
+      - execute_code
+  messaging:
+    publishes:
+      - channel: reviews.feedback
+        description: Code review feedback for merge requests
+        schema:
+          type: object
+          properties:
+            mr_id:
+              type: integer
+            feedback_type:
+              type: string
+              enum:
+                - comment
+                - request_changes
+                - praise
+            issues_found:
+              type: array
+            recommendations:
+              type: array