# Skeen Reference Agent Blueprint # Specification: Vendor-Neutral Multi-Agent Governance Manifest # License: MIT (Reference Architecture Specification) apiVersion: architecture.skeen.biz/v1alpha1 kind: AgentBlueprint metadata: id: scope-signed-posture-runner name: Cryptographically Signed Security Posture Runner version: "1.2.0" lane: security-posture-discovery classification: cryptographic-scope-gated-discovery summary: >- Verifies an offline Ed25519/cosign-signed scope authorization manifest before executing any discovery probe; refuses unsigned targets, expired windows, or in-house exemptions; emits a deterministic, plain-English posture briefing. governance: lethal_trifecta_controls: reads_raw_untrusted_payloads: true holds_system_of_record_write_credentials: false autonomous_external_egress: false rationale: >- Because discovery probes inspect potentially untrusted network banners and headers, the runner executes in an isolated environment with zero internal vault credentials and no outbound communication channel outside the cryptographically signed target CIDR/domain list. scope: pre_execution_cryptographic_gate: manifest_schema: "schemas/signed-scope-manifest-v1.json" signature_algorithm: Ed25519 public_key_pinning: offline-pinned-verifier-key mandatory_checks: - valid_ed25519_signature == true - current_utc_within_authorized_window == true - target_in_signed_allowlist == true - allow_inhouse_exemptions == false on_verification_failure: abort-immediately-exit-nonzero permitted_read_scope: - source: authorized-target-cidrs-and-hostnames access: non-intrusive-read-only-discovery checks: - listening-service-and-tls-posture - default-or-exposed-management-interfaces - dns-mail-authentication-spf-dkim-dmarc - external-header-and-redirect-hygiene hard_write_boundary: never_autonomous: - Probing any IP, subnet, or hostname absent from the signed scope manifest - Running exploit payloads, brute-force authentication attempts, or denial-of-service traffic - Modifying client firewall rules, router configurations, or endpoint settings - Uploading client discovery telemetry to third-party cloud LLM endpoints enforcement_mechanism: >- Hard pre-flight signature verification gate compiled into the runner entrypoint; network egress is restricted to the target list extracted from the verified manifest. verification_and_audit: artifact_name: Scope-Verified Posture Briefing & Evidence Pack artifact_format: Deterministic JSON Findings + Executive Markdown Summary required_fields: - scope_manifest_sha256 - signer_key_fingerprint - authorization_window_utc - targets_evaluated_count - top_three_prioritized_remediations - raw_evidence_checksums