@raishin/vanguard-frontier-agentic 3.19.0 → 3.21.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +2 -2
- package/.claude-plugin/plugin.json +13 -1
- package/.cursor-plugin/plugin.json +13 -1
- package/.github/plugin/marketplace.json +1 -1
- package/README.md +25 -23
- package/agents/AGENTS.md +4 -4
- package/agents/README.md +7 -7
- package/agents/alibaba/alibaba-tablestore-architect-agent/AGENT.md +54 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/codex.toml +11 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/alibaba/alibaba-tablestore-architect-agent/metadata.json +39 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/AGENT.md +50 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/LEAST-PRIVILEGES.md +23 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/README.md +36 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/claude-code.agent.md +44 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/codex.toml +51 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/copilot.agent.md +71 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/cursor.agent.md +43 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/gemini.agent.md +44 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/harnesses/kiro-ide.agent.md +43 -0
- package/agents/atlassian/atlassian-control-evidence-lineage-agent/metadata.json +43 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/AGENT.md +49 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/LEAST-PRIVILEGES.md +23 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/README.md +36 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/claude-code.agent.md +43 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/codex.toml +51 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/copilot.agent.md +70 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/cursor.agent.md +42 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/gemini.agent.md +43 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/harnesses/kiro-ide.agent.md +42 -0
- package/agents/atlassian/atlassian-incident-prevention-agent/metadata.json +43 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/AGENT.md +48 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/LEAST-PRIVILEGES.md +23 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/README.md +36 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/claude-code.agent.md +42 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/codex.toml +47 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/copilot.agent.md +69 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/cursor.agent.md +41 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/gemini.agent.md +42 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/harnesses/kiro-ide.agent.md +41 -0
- package/agents/atlassian/atlassian-knowledge-integrity-agent/metadata.json +42 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/AGENT.md +51 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/LEAST-PRIVILEGES.md +23 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/README.md +36 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/claude-code.agent.md +45 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/codex.toml +52 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/copilot.agent.md +72 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/cursor.agent.md +44 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/gemini.agent.md +45 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/harnesses/kiro-ide.agent.md +44 -0
- package/agents/atlassian/atlassian-live-write-guard-agent/metadata.json +43 -0
- package/agents/atlassian/atlassian-maestro-agent/AGENT.md +49 -0
- package/agents/atlassian/atlassian-maestro-agent/LEAST-PRIVILEGES.md +20 -0
- package/agents/atlassian/atlassian-maestro-agent/README.md +36 -0
- package/agents/atlassian/atlassian-maestro-agent/harnesses/claude-code.agent.md +43 -0
- package/agents/atlassian/atlassian-maestro-agent/harnesses/codex.toml +44 -0
- package/agents/atlassian/atlassian-maestro-agent/harnesses/copilot.agent.md +46 -0
- package/agents/atlassian/atlassian-maestro-agent/harnesses/cursor.agent.md +42 -0
- package/agents/atlassian/atlassian-maestro-agent/harnesses/gemini.agent.md +43 -0
- package/agents/atlassian/atlassian-maestro-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/atlassian/atlassian-maestro-agent/harnesses/kiro-ide.agent.md +42 -0
- package/agents/atlassian/atlassian-maestro-agent/metadata.json +41 -0
- package/agents/aws/aws-dynamodb-patterns-agent/AGENT.md +53 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/codex.toml +23 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/copilot.agent.md +42 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/cursor.agent.md +38 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/gemini.agent.md +38 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/aws/aws-dynamodb-patterns-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/aws/aws-dynamodb-patterns-agent/metadata.json +39 -0
- package/agents/azure/azure-cosmosdb-application-developer-agent/metadata.json +4 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/AGENT.md +53 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/codex.toml +23 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/copilot.agent.md +42 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/cursor.agent.md +37 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/gemini.agent.md +38 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/azure/azure-cosmosdb-pattern-agent/metadata.json +38 -0
- package/agents/gcp/gcp-bigtable-architect-agent/AGENT.md +54 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/codex.toml +11 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/gcp/gcp-bigtable-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/gcp/gcp-bigtable-architect-agent/metadata.json +39 -0
- package/agents/huawei/huawei-geminidb-architect-agent/AGENT.md +54 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/codex.toml +11 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/cursor.agent.md +38 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/huawei/huawei-geminidb-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/huawei/huawei-geminidb-architect-agent/metadata.json +38 -0
- package/agents/oci/oci-nosql-database-architect-agent/AGENT.md +54 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/claude-code.agent.md +37 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/codex.toml +11 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/copilot.agent.md +43 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/cursor.agent.md +39 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/gemini.agent.md +39 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/oci/oci-nosql-database-architect-agent/harnesses/kiro-ide.agent.md +37 -0
- package/agents/oci/oci-nosql-database-architect-agent/metadata.json +39 -0
- package/agents/oci/oci-nosql-pattern-agent/AGENT.md +53 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/claude-code.agent.md +36 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/codex.toml +23 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/copilot.agent.md +42 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/cursor.agent.md +38 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/gemini.agent.md +38 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-cli.agent.json +5 -0
- package/agents/oci/oci-nosql-pattern-agent/harnesses/kiro-ide.agent.md +36 -0
- package/agents/oci/oci-nosql-pattern-agent/metadata.json +38 -0
- package/catalog/agents.json +366 -1
- package/catalog/asset-integrity.json +1686 -81
- package/catalog/install-roles.json +41 -1
- package/catalog/model-assignments.json +396 -0
- package/catalog/skill-manifest.json +2429 -194
- package/catalog/skills.json +544 -14
- package/mods/live-guard-gate/lib/live-agents.mjs +1 -0
- package/package.json +8 -2
- package/plugins/vanguard-frontier-agentic/.codex-plugin/plugin.json +1 -1
- package/powers/README.md +3 -2
- package/powers/vanguard-alibaba/POWER.md +1 -1
- package/powers/vanguard-atlassian/POWER.md +42 -0
- package/powers/vanguard-aws/POWER.md +1 -1
- package/powers/vanguard-azure/POWER.md +1 -1
- package/powers/vanguard-gcp/POWER.md +1 -1
- package/powers/vanguard-huawei/POWER.md +1 -1
- package/powers/vanguard-oci/POWER.md +1 -1
- package/schemas/agent.schema.json +1 -0
- package/schemas/skill.schema.json +1 -0
- package/scripts/export-marketplace-agents.mjs +4 -1
- package/scripts/generate-docs-data.mjs +1 -0
- package/scripts/generate-kiro-powers.mjs +15 -0
- package/skills/alibaba/README.md +2 -1
- package/skills/alibaba/alibaba-maestro/SKILL.md +2 -1
- package/skills/alibaba/alibaba-tablestore-architect/SKILL.md +69 -0
- package/skills/alibaba/alibaba-tablestore-architect/metadata.json +28 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/live.md +110 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit/offline.md +119 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/commands/audit.md +22 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/evidence-ledger.md +87 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/operations.md +190 -0
- package/skills/alibaba/alibaba-tablestore-architect/references/tablestore-design-guide.md +159 -0
- package/skills/atlassian/atlassian-control-evidence-lineage/SKILL.md +52 -0
- package/skills/atlassian/atlassian-control-evidence-lineage/metadata.json +18 -0
- package/skills/atlassian/atlassian-control-evidence-lineage/references/lineage-model.md +59 -0
- package/skills/atlassian/atlassian-control-evidence-lineage/references/workflow-and-output.md +69 -0
- package/skills/atlassian/atlassian-incident-prevention-review/SKILL.md +61 -0
- package/skills/atlassian/atlassian-incident-prevention-review/metadata.json +19 -0
- package/skills/atlassian/atlassian-incident-prevention-review/references/recurrence-evidence.md +92 -0
- package/skills/atlassian/atlassian-incident-prevention-review/references/workflow-and-output.md +118 -0
- package/skills/atlassian/atlassian-knowledge-integrity-review/SKILL.md +64 -0
- package/skills/atlassian/atlassian-knowledge-integrity-review/metadata.json +19 -0
- package/skills/atlassian/atlassian-knowledge-integrity-review/references/staleness-and-history.md +89 -0
- package/skills/atlassian/atlassian-knowledge-integrity-review/references/workflow-and-output.md +99 -0
- package/skills/atlassian/atlassian-live-write-guard/SKILL.md +51 -0
- package/skills/atlassian/atlassian-live-write-guard/metadata.json +18 -0
- package/skills/atlassian/atlassian-live-write-guard/references/authorization-checklist.md +39 -0
- package/skills/atlassian/atlassian-live-write-guard/references/write-verification.md +47 -0
- package/skills/atlassian/atlassian-rovo-mcp-integration/SKILL.md +72 -0
- package/skills/atlassian/atlassian-rovo-mcp-integration/metadata.json +26 -0
- package/skills/atlassian/atlassian-rovo-mcp-integration/references/auth-tenant-and-trust-boundaries.md +59 -0
- package/skills/atlassian/atlassian-rovo-mcp-integration/references/evidence-ledger.md +36 -0
- package/skills/atlassian/atlassian-rovo-mcp-integration/references/failure-and-recovery.md +36 -0
- package/skills/atlassian/atlassian-rovo-mcp-integration/references/tool-risk-tiers.md +91 -0
- package/skills/atlassian/confluence-document-authoring/CHANGELOG.md +28 -0
- package/skills/atlassian/confluence-document-authoring/SKILL.md +70 -0
- package/skills/atlassian/confluence-document-authoring/agents/openai.yaml +15 -0
- package/skills/atlassian/confluence-document-authoring/assets/examples/adr-example.md +81 -0
- package/skills/atlassian/confluence-document-authoring/assets/examples/business-product-explainer.md +99 -0
- package/skills/atlassian/confluence-document-authoring/assets/examples/feature-rollout-brief.md +108 -0
- package/skills/atlassian/confluence-document-authoring/assets/examples/queue-backlog-runbook.md +158 -0
- package/skills/atlassian/confluence-document-authoring/assets/examples/retry-contract-adr.md +99 -0
- package/skills/atlassian/confluence-document-authoring/assets/icon.svg +8 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/adr.md +87 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/api-documentation.md +97 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/customer-impact-assessment.md +43 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/experiment-plan-results.md +44 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/feature-overview.md +79 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/how-to.md +58 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/incident-playbook.md +89 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/incident-postmortem.md +83 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/meeting-notes.md +86 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/okrs.md +51 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/prd.md +83 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/product-explainer.md +77 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/product-roadmap.md +54 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/project-charter.md +56 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/project-plan.md +52 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/project-status-report.md +47 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/release-notes.md +119 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/risk-assessment.md +40 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/runbook.md +87 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/sprint-retrospective.md +85 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/support-knowledge-base.md +79 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/tdd.md +97 -0
- package/skills/atlassian/confluence-document-authoring/assets/templates/team-working-agreement.md +46 -0
- package/skills/atlassian/confluence-document-authoring/manifest.json +260 -0
- package/skills/atlassian/confluence-document-authoring/metadata.json +26 -0
- package/skills/atlassian/confluence-document-authoring/prompts/README.md +21 -0
- package/skills/atlassian/confluence-document-authoring/prompts/customer-impact-assessment.md +14 -0
- package/skills/atlassian/confluence-document-authoring/prompts/experiment-plan-results.md +14 -0
- package/skills/atlassian/confluence-document-authoring/prompts/feature-overview.md +22 -0
- package/skills/atlassian/confluence-document-authoring/prompts/okrs.md +14 -0
- package/skills/atlassian/confluence-document-authoring/prompts/product-explainer.md +20 -0
- package/skills/atlassian/confluence-document-authoring/prompts/product-idea-to-prd-and-backlog.md +20 -0
- package/skills/atlassian/confluence-document-authoring/prompts/product-roadmap.md +14 -0
- package/skills/atlassian/confluence-document-authoring/prompts/project-charter.md +14 -0
- package/skills/atlassian/confluence-document-authoring/prompts/project-plan.md +14 -0
- package/skills/atlassian/confluence-document-authoring/prompts/project-status-report.md +14 -0
- package/skills/atlassian/confluence-document-authoring/prompts/release-notes.md +16 -0
- package/skills/atlassian/confluence-document-authoring/prompts/risk-assessment.md +14 -0
- package/skills/atlassian/confluence-document-authoring/prompts/support-knowledge-base.md +21 -0
- package/skills/atlassian/confluence-document-authoring/prompts/team-working-agreement.md +14 -0
- package/skills/atlassian/confluence-document-authoring/references/audience-patterns.md +43 -0
- package/skills/atlassian/confluence-document-authoring/references/cql-patterns.md +53 -0
- package/skills/atlassian/confluence-document-authoring/references/jira-integration.md +47 -0
- package/skills/atlassian/confluence-document-authoring/references/lifecycle.md +55 -0
- package/skills/atlassian/confluence-document-authoring/references/publishing.md +41 -0
- package/skills/atlassian/confluence-document-authoring/references/quality-review.md +56 -0
- package/skills/atlassian/confluence-document-authoring/references/sources.md +47 -0
- package/skills/atlassian/confluence-document-authoring/references/template-catalogue.md +30 -0
- package/skills/atlassian/confluence-document-authoring/references/template-maintenance.md +32 -0
- package/skills/atlassian/jira-ticket-authoring/CHANGELOG.md +26 -0
- package/skills/atlassian/jira-ticket-authoring/SKILL.md +70 -0
- package/skills/atlassian/jira-ticket-authoring/agents/openai.yaml +14 -0
- package/skills/atlassian/jira-ticket-authoring/assets/examples/customer-export-support.md +85 -0
- package/skills/atlassian/jira-ticket-authoring/assets/examples/implementation-example.md +70 -0
- package/skills/atlassian/jira-ticket-authoring/assets/examples/invoice-retry-bug.md +87 -0
- package/skills/atlassian/jira-ticket-authoring/assets/examples/sparse-request-triage.md +84 -0
- package/skills/atlassian/jira-ticket-authoring/assets/icon.svg +8 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/agent-handoff.md +49 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/bug.md +62 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/epic.md +68 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/feature-request.md +59 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/finding.md +68 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/implementation.md +96 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/incident.md +63 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/operational-change.md +84 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/service-request.md +59 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/spike.md +52 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/story.md +59 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/support-case.md +59 -0
- package/skills/atlassian/jira-ticket-authoring/assets/templates/tech-debt.md +48 -0
- package/skills/atlassian/jira-ticket-authoring/manifest.json +174 -0
- package/skills/atlassian/jira-ticket-authoring/metadata.json +26 -0
- package/skills/atlassian/jira-ticket-authoring/prompts/README.md +11 -0
- package/skills/atlassian/jira-ticket-authoring/prompts/access-or-service-request.md +16 -0
- package/skills/atlassian/jira-ticket-authoring/prompts/bug-report.md +21 -0
- package/skills/atlassian/jira-ticket-authoring/prompts/customer-support-case.md +18 -0
- package/skills/atlassian/jira-ticket-authoring/prompts/epic-breakdown.md +14 -0
- package/skills/atlassian/jira-ticket-authoring/prompts/new-feature-request.md +16 -0
- package/skills/atlassian/jira-ticket-authoring/prompts/product-idea-to-prd-and-backlog.md +20 -0
- package/skills/atlassian/jira-ticket-authoring/prompts/user-story.md +14 -0
- package/skills/atlassian/jira-ticket-authoring/references/adversarial-review.md +17 -0
- package/skills/atlassian/jira-ticket-authoring/references/jira-confluence-traceability.md +32 -0
- package/skills/atlassian/jira-ticket-authoring/references/jira-integration.md +47 -0
- package/skills/atlassian/jira-ticket-authoring/references/planning-patterns.md +57 -0
- package/skills/atlassian/jira-ticket-authoring/references/quality-review.md +49 -0
- package/skills/atlassian/jira-ticket-authoring/references/service-routing.md +44 -0
- package/skills/atlassian/jira-ticket-authoring/references/sources.md +33 -0
- package/skills/atlassian/jira-ticket-authoring/references/template-adaptation.md +29 -0
- package/skills/aws/aws-documentdb-architect/SKILL.md +43 -0
- package/skills/aws/aws-documentdb-architect/metadata.json +26 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit/live.md +135 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit/offline.md +127 -0
- package/skills/aws/aws-documentdb-architect/references/commands/audit.md +23 -0
- package/skills/aws/aws-documentdb-architect/references/evidence-ledger.md +52 -0
- package/skills/aws/aws-documentdb-architect/references/official-sources.md +15 -0
- package/skills/aws/aws-documentdb-architect/references/operations.md +165 -0
- package/skills/aws/aws-documentdb-architect/references/safety-checklist.md +22 -0
- package/skills/aws/aws-documentdb-architect/references/workflow-and-output.md +22 -0
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/SKILL.md +5 -3
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/metadata.json +7 -3
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/consistency-indexing-replication.md +103 -0
- package/skills/aws/aws-dynamodb-data-modeling-performance-review/references/evidence-ledger.md +38 -0
- package/skills/aws/aws-dynamodb-patterns/CHANGELOG.md +87 -0
- package/skills/aws/aws-dynamodb-patterns/README.md +132 -0
- package/skills/aws/aws-dynamodb-patterns/SKILL.md +82 -0
- package/skills/aws/aws-dynamodb-patterns/assets/bedrock-embedding-input.json +6 -0
- package/skills/aws/aws-dynamodb-patterns/assets/content-review.json +6 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table-with-lsi.json +41 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table.json +27 -0
- package/skills/aws/aws-dynamodb-patterns/assets/create-table.sh +37 -0
- package/skills/aws/aws-dynamodb-patterns/assets/embedding-flow.py +89 -0
- package/skills/aws/aws-dynamodb-patterns/assets/query-input.json +13 -0
- package/skills/aws/aws-dynamodb-patterns/assets/query-pages.mjs +54 -0
- package/skills/aws/aws-dynamodb-patterns/assets/stream-read-policy.json +11 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table-index-read-policy.json +20 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table-resource-policy.json +22 -0
- package/skills/aws/aws-dynamodb-patterns/assets/table.cfn.yaml +55 -0
- package/skills/aws/aws-dynamodb-patterns/assets/typed-vector-item.json +15 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-create-table.json +23 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-search-policy.json +11 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-search.json +10 -0
- package/skills/aws/aws-dynamodb-patterns/assets/vector-table.cfn.yaml +41 -0
- package/skills/aws/aws-dynamodb-patterns/evals/audit.test.py +87 -0
- package/skills/aws/aws-dynamodb-patterns/evals/backup-restore.test.py +163 -0
- package/skills/aws/aws-dynamodb-patterns/evals/commands.test.py +185 -0
- package/skills/aws/aws-dynamodb-patterns/evals/create-table.test.py +99 -0
- package/skills/aws/aws-dynamodb-patterns/evals/data-vectors-maintenance.test.py +201 -0
- package/skills/aws/aws-dynamodb-patterns/evals/embedding-commands.test.py +162 -0
- package/skills/aws/aws-dynamodb-patterns/evals/embedding-flow.test.py +167 -0
- package/skills/aws/aws-dynamodb-patterns/evals/eval.md +328 -0
- package/skills/aws/aws-dynamodb-patterns/evals/evals.json +185 -0
- package/skills/aws/aws-dynamodb-patterns/evals/modes.test.py +195 -0
- package/skills/aws/aws-dynamodb-patterns/evals/operations.test.py +288 -0
- package/skills/aws/aws-dynamodb-patterns/evals/query-pages.test.mjs +156 -0
- package/skills/aws/aws-dynamodb-patterns/evals/readme-and-loading.test.py +69 -0
- package/skills/aws/aws-dynamodb-patterns/evals/verify.py +166 -0
- package/skills/aws/aws-dynamodb-patterns/metadata.json +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/README.md +32 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit/live.md +64 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit/offline.md +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/audit.md +65 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/aws-cli.md +206 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup/on-demand.md +36 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup/pitr.md +41 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/backup.md +27 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/design.md +47 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/embedding.md +200 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/feature-plan.md +56 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/help.md +28 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/performance-test.md +95 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/recovery-target.md +47 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/refactor.md +82 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore/on-demand.md +32 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore/pitr.md +42 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/restore.md +76 -0
- package/skills/aws/aws-dynamodb-patterns/references/commands/select.md +22 -0
- package/skills/aws/aws-dynamodb-patterns/references/data-types-and-vectors.md +175 -0
- package/skills/aws/aws-dynamodb-patterns/references/embedding-integrations.md +237 -0
- package/skills/aws/aws-dynamodb-patterns/references/encryption.md +156 -0
- package/skills/aws/aws-dynamodb-patterns/references/evidence-index.md +116 -0
- package/skills/aws/aws-dynamodb-patterns/references/evidence-ledger.md +373 -0
- package/skills/aws/aws-dynamodb-patterns/references/iam-and-access.md +173 -0
- package/skills/aws/aws-dynamodb-patterns/references/language-adapters.md +251 -0
- package/skills/aws/aws-dynamodb-patterns/references/lsi-vs-gsi.md +116 -0
- package/skills/aws/aws-dynamodb-patterns/references/maintenance.md +56 -0
- package/skills/aws/aws-dynamodb-patterns/references/modeling.md +131 -0
- package/skills/aws/aws-dynamodb-patterns/references/monitoring.md +137 -0
- package/skills/aws/aws-dynamodb-patterns/references/official-sources.md +34 -0
- package/skills/aws/aws-dynamodb-patterns/references/operations.md +130 -0
- package/skills/aws/aws-dynamodb-patterns/references/provisioning.md +110 -0
- package/skills/aws/aws-dynamodb-patterns/references/recovery-and-replicas.md +148 -0
- package/skills/aws/aws-dynamodb-patterns/references/runtime-contract.md +140 -0
- package/skills/aws/aws-dynamodb-patterns/references/safety-checklist.md +35 -0
- package/skills/aws/aws-dynamodb-patterns/references/sources.md +170 -0
- package/skills/aws/aws-dynamodb-patterns/references/streams-and-dax.md +160 -0
- package/skills/aws/aws-dynamodb-patterns/references/workflow-and-output.md +34 -0
- package/skills/aws/aws-dynamodb-patterns/references/workflow.md +133 -0
- package/skills/aws/aws-dynamodb-patterns/scripts/review_due.py +61 -0
- package/skills/aws/aws-dynamodb-patterns/scripts/select_mode.py +127 -0
- package/skills/aws/aws-keyspaces-architect/SKILL.md +43 -0
- package/skills/aws/aws-keyspaces-architect/metadata.json +26 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit/live.md +118 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit/offline.md +125 -0
- package/skills/aws/aws-keyspaces-architect/references/commands/audit.md +22 -0
- package/skills/aws/aws-keyspaces-architect/references/evidence-ledger.md +49 -0
- package/skills/aws/aws-keyspaces-architect/references/official-sources.md +15 -0
- package/skills/aws/aws-keyspaces-architect/references/operations.md +154 -0
- package/skills/aws/aws-keyspaces-architect/references/safety-checklist.md +22 -0
- package/skills/aws/aws-keyspaces-architect/references/workflow-and-output.md +22 -0
- package/skills/aws/aws-maestro/SKILL.md +1 -1
- package/skills/aws/aws-maestro/metadata.json +1 -1
- package/skills/aws/aws-maestro/references/workflow-and-output.md +1 -0
- package/skills/azure/azure-cosmosdb-application-developer/SKILL.md +4 -2
- package/skills/azure/azure-cosmosdb-application-developer/metadata.json +1 -1
- package/skills/azure/azure-cosmosdb-pattern/CHANGELOG.md +10 -0
- package/skills/azure/azure-cosmosdb-pattern/README.md +102 -0
- package/skills/azure/azure-cosmosdb-pattern/SKILL.md +69 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/account.arm.json +59 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/content-review.json +9 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/indexing-policy.json +7 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/order.json +10 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/provision.sh +32 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/runtime.mjs +99 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/vector-indexing-policy.json +7 -0
- package/skills/azure/azure-cosmosdb-pattern/assets/vector-policy.json +3 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/eval.md +32 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/fixtures/recovery-continuous.json +28 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/prompts.json +24 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/report.md +54 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/runtime.test.mjs +146 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/source-evidence.json +28 -0
- package/skills/azure/azure-cosmosdb-pattern/evals/test_package.py +355 -0
- package/skills/azure/azure-cosmosdb-pattern/metadata.json +25 -0
- package/skills/azure/azure-cosmosdb-pattern/references/access-control.md +42 -0
- package/skills/azure/azure-cosmosdb-pattern/references/change-feed-and-integrations.md +31 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/live.md +17 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit/offline.md +15 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/audit.md +8 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/azure-cli.md +39 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/continuous.md +30 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup/periodic.md +28 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/backup.md +11 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/design.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/feature-plan.md +18 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/help.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/performance-test.md +24 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/recovery-target.md +30 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/refactor.md +14 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-deleted-resource.md +55 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/continuous-new-account.md +50 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore/periodic-support.md +27 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/restore.md +13 -0
- package/skills/azure/azure-cosmosdb-pattern/references/commands/select.md +11 -0
- package/skills/azure/azure-cosmosdb-pattern/references/data-types-and-vectors.md +51 -0
- package/skills/azure/azure-cosmosdb-pattern/references/embedding-integrations.md +56 -0
- package/skills/azure/azure-cosmosdb-pattern/references/encryption.md +53 -0
- package/skills/azure/azure-cosmosdb-pattern/references/evidence-index.md +72 -0
- package/skills/azure/azure-cosmosdb-pattern/references/evidence-ledger.md +174 -0
- package/skills/azure/azure-cosmosdb-pattern/references/indexing-and-capacity.md +37 -0
- package/skills/azure/azure-cosmosdb-pattern/references/language-adapters.md +112 -0
- package/skills/azure/azure-cosmosdb-pattern/references/maintenance.md +19 -0
- package/skills/azure/azure-cosmosdb-pattern/references/modeling.md +44 -0
- package/skills/azure/azure-cosmosdb-pattern/references/monitoring.md +23 -0
- package/skills/azure/azure-cosmosdb-pattern/references/provisioning.md +61 -0
- package/skills/azure/azure-cosmosdb-pattern/references/recovery.md +31 -0
- package/skills/azure/azure-cosmosdb-pattern/references/replication.md +22 -0
- package/skills/azure/azure-cosmosdb-pattern/references/runtime-contract.md +43 -0
- package/skills/azure/azure-cosmosdb-pattern/references/sources.md +61 -0
- package/skills/azure/azure-cosmosdb-pattern/references/workflow.md +18 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/recovery_guard.py +96 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/review_due.py +26 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/select_mode.py +108 -0
- package/skills/azure/azure-cosmosdb-pattern/scripts/validate_assets.py +53 -0
- package/skills/azure/azure-cosmosdb-platform-operator/SKILL.md +6 -2
- package/skills/azure/azure-cosmosdb-platform-operator/metadata.json +6 -3
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/live.md +180 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit/offline.md +160 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/commands/audit.md +26 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/consistency-capacity-security.md +136 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/cosmosdb-platform-operations.md +1 -1
- package/skills/azure/azure-cosmosdb-platform-operator/references/evidence-ledger.md +242 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations-cassandra.md +178 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations-mongodb.md +202 -0
- package/skills/azure/azure-cosmosdb-platform-operator/references/operations.md +126 -0
- package/skills/azure/azure-maestro/SKILL.md +1 -0
- package/skills/cross-functional/atlassian-case-capsule/SKILL.md +49 -0
- package/skills/cross-functional/atlassian-case-capsule/assets/atlassian-case-capsule.schema.json +487 -0
- package/skills/cross-functional/atlassian-case-capsule/metadata.json +25 -0
- package/skills/cross-functional/atlassian-case-capsule/scripts/validate_capsule.py +499 -0
- package/skills/cross-functional/atlassian-routing-protocol/SKILL.md +67 -0
- package/skills/cross-functional/atlassian-routing-protocol/metadata.json +18 -0
- package/skills/gcp/README.md +2 -1
- package/skills/gcp/gcp-bigtable-architect/SKILL.md +71 -0
- package/skills/gcp/gcp-bigtable-architect/metadata.json +28 -0
- package/skills/gcp/gcp-bigtable-architect/references/bigtable-design-guide.md +156 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit/live.md +122 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit/offline.md +140 -0
- package/skills/gcp/gcp-bigtable-architect/references/commands/audit.md +21 -0
- package/skills/gcp/gcp-bigtable-architect/references/evidence-ledger.md +83 -0
- package/skills/gcp/gcp-bigtable-architect/references/operations.md +111 -0
- package/skills/gcp/gcp-firebase-developer/SKILL.md +6 -3
- package/skills/gcp/gcp-firebase-developer/metadata.json +14 -4
- package/skills/gcp/gcp-firebase-developer/references/commands/audit/live.md +124 -0
- package/skills/gcp/gcp-firebase-developer/references/commands/audit/offline.md +146 -0
- package/skills/gcp/gcp-firebase-developer/references/commands/audit.md +27 -0
- package/skills/gcp/gcp-firebase-developer/references/evidence-ledger.md +190 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore-mongodb-operations.md +189 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore-operations.md +202 -0
- package/skills/gcp/gcp-firebase-developer/references/firestore.md +122 -0
- package/skills/gcp/gcp-maestro/SKILL.md +2 -1
- package/skills/huawei/README.md +2 -1
- package/skills/huawei/huawei-gaussdb-rds-dba/SKILL.md +7 -4
- package/skills/huawei/huawei-gaussdb-rds-dba/metadata.json +12 -4
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/live.md +68 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit/offline.md +106 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/commands/audit.md +23 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/dds-operations.md +135 -0
- package/skills/huawei/huawei-gaussdb-rds-dba/references/evidence-ledger.md +87 -0
- package/skills/huawei/huawei-geminidb-architect/SKILL.md +68 -0
- package/skills/huawei/huawei-geminidb-architect/metadata.json +26 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit/live.md +68 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit/offline.md +108 -0
- package/skills/huawei/huawei-geminidb-architect/references/commands/audit.md +23 -0
- package/skills/huawei/huawei-geminidb-architect/references/evidence-ledger.md +83 -0
- package/skills/huawei/huawei-geminidb-architect/references/geminidb-design-guide.md +114 -0
- package/skills/huawei/huawei-geminidb-architect/references/operations.md +135 -0
- package/skills/huawei/huawei-maestro/SKILL.md +2 -1
- package/skills/ionos/ionos-live-database-lifecycle-guard/SKILL.md +2 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/live.md +87 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit/offline.md +109 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/commands/audit.md +27 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/evidence-ledger.md +69 -0
- package/skills/ionos/ionos-live-database-lifecycle-guard/references/mongodb-operations.md +220 -0
- package/skills/oci/README.md +6 -1
- package/skills/oci/oci-nosql-database-architect/SKILL.md +73 -0
- package/skills/oci/oci-nosql-database-architect/metadata.json +28 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit/live.md +136 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit/offline.md +150 -0
- package/skills/oci/oci-nosql-database-architect/references/commands/audit.md +28 -0
- package/skills/oci/oci-nosql-database-architect/references/evidence-ledger.md +96 -0
- package/skills/oci/oci-nosql-database-architect/references/nosql-design-guide.md +194 -0
- package/skills/oci/oci-nosql-database-architect/references/operations.md +194 -0
- package/skills/oci/oci-nosql-database-architect/references/sdk-matrix.md +43 -0
- package/skills/oci/oci-nosql-pattern/CHANGELOG.md +8 -0
- package/skills/oci/oci-nosql-pattern/README.md +81 -0
- package/skills/oci/oci-nosql-pattern/SKILL.md +62 -0
- package/skills/oci/oci-nosql-pattern/assets/content-review.json +10 -0
- package/skills/oci/oci-nosql-pattern/assets/create-table.sh +32 -0
- package/skills/oci/oci-nosql-pattern/assets/index-keys.json +11 -0
- package/skills/oci/oci-nosql-pattern/assets/migrator-export.json +22 -0
- package/skills/oci/oci-nosql-pattern/assets/migrator-import.json +29 -0
- package/skills/oci/oci-nosql-pattern/assets/orders.ddl +9 -0
- package/skills/oci/oci-nosql-pattern/assets/orders.tf +46 -0
- package/skills/oci/oci-nosql-pattern/assets/query-pages.mjs +33 -0
- package/skills/oci/oci-nosql-pattern/assets/query.json +13 -0
- package/skills/oci/oci-nosql-pattern/assets/query.sql +1 -0
- package/skills/oci/oci-nosql-pattern/assets/recovery-manifest.example.json +35 -0
- package/skills/oci/oci-nosql-pattern/assets/row.json +10 -0
- package/skills/oci/oci-nosql-pattern/assets/table-limits.json +6 -0
- package/skills/oci/oci-nosql-pattern/evals/cli-shapes.json +222 -0
- package/skills/oci/oci-nosql-pattern/evals/eval.md +26 -0
- package/skills/oci/oci-nosql-pattern/evals/prompts.json +89 -0
- package/skills/oci/oci-nosql-pattern/evals/report.md +41 -0
- package/skills/oci/oci-nosql-pattern/evals/test_package.py +350 -0
- package/skills/oci/oci-nosql-pattern/evals/test_runtime.mjs +77 -0
- package/skills/oci/oci-nosql-pattern/metadata.json +25 -0
- package/skills/oci/oci-nosql-pattern/references/access.md +29 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit/live.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit/offline.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/audit.md +6 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup/migrator.md +12 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup/sdk.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/backup.md +7 -0
- package/skills/oci/oci-nosql-pattern/references/commands/design.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/feature-plan.md +10 -0
- package/skills/oci/oci-nosql-pattern/references/commands/help.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/performance-test.md +12 -0
- package/skills/oci/oci-nosql-pattern/references/commands/refactor.md +9 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore/migrator.md +13 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore/sdk.md +11 -0
- package/skills/oci/oci-nosql-pattern/references/commands/restore.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/commands/select.md +8 -0
- package/skills/oci/oci-nosql-pattern/references/embedding-integrations.md +25 -0
- package/skills/oci/oci-nosql-pattern/references/encryption.md +18 -0
- package/skills/oci/oci-nosql-pattern/references/evidence-index.md +44 -0
- package/skills/oci/oci-nosql-pattern/references/evidence-ledger.md +73 -0
- package/skills/oci/oci-nosql-pattern/references/indexes.md +19 -0
- package/skills/oci/oci-nosql-pattern/references/language-adapters.md +160 -0
- package/skills/oci/oci-nosql-pattern/references/maintenance.md +15 -0
- package/skills/oci/oci-nosql-pattern/references/modeling.md +26 -0
- package/skills/oci/oci-nosql-pattern/references/monitoring.md +21 -0
- package/skills/oci/oci-nosql-pattern/references/provisioning.md +44 -0
- package/skills/oci/oci-nosql-pattern/references/recovery-boundary.md +32 -0
- package/skills/oci/oci-nosql-pattern/references/replicas.md +18 -0
- package/skills/oci/oci-nosql-pattern/references/runtime-contract.md +23 -0
- package/skills/oci/oci-nosql-pattern/references/sources.md +57 -0
- package/skills/oci/oci-nosql-pattern/references/ttl.md +19 -0
- package/skills/oci/oci-nosql-pattern/references/types-and-vectors.md +27 -0
- package/skills/oci/oci-nosql-pattern/scripts/check_recovery.py +52 -0
- package/skills/oci/oci-nosql-pattern/scripts/review_due.py +32 -0
- package/skills/oci/oci-nosql-pattern/scripts/select_mode.py +96 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/SKILL.md +43 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/metadata.json +25 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/live.md +90 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit/offline.md +112 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/commands/audit.md +24 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/evidence-ledger.md +93 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/official-sources.md +15 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/operations.md +216 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/safety-checklist.md +22 -0
- package/skills/ovhcloud/ovhcloud-mongodb-architect/references/workflow-and-output.md +22 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/SKILL.md +43 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/metadata.json +24 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/live.md +99 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit/offline.md +114 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/commands/audit.md +24 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/evidence-ledger.md +43 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/official-sources.md +14 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/operations.md +114 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/safety-checklist.md +22 -0
- package/skills/scaleway/scaleway-managed-mongodb-architect/references/workflow-and-output.md +22 -0
- package/templates/nosql-audit-template.md +127 -0
- package/templates/nosql-operations-template.md +60 -0
- package/tests/_generate_maestro_routing_fixtures.py +15 -0
- package/tests/fixtures/README.md +3 -3
- package/tests/fixtures/alibaba-maestro-routing/expected/050-happy-tablestore-partition-key.json +6 -0
- package/tests/fixtures/alibaba-maestro-routing/expected/adv-tablestore-not-polardb.json +6 -0
- package/tests/fixtures/alibaba-maestro-routing/inputs/050-happy-tablestore-partition-key.json +7 -0
- package/tests/fixtures/alibaba-maestro-routing/inputs/adv-tablestore-not-polardb.json +7 -0
- package/tests/fixtures/alibaba-maestro-routing/taxonomy.json +13 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/01-forged-approval-jira-comment.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/02-approval-points-at-untrusted-content.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/03-approval-relayed-by-agent.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/04-approval-from-chat-transcript.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/05-agent-approves-write.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/06-service-account-approves-write.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/07-expired-approval.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/08-approval-dated-after-as-of.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/09-write-with-pending-approval.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/10-prohibited-decide-jsm-approval.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/11-prohibited-approve-resolver-plans.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/12-prohibited-restriction-change.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/13-prohibited-permission-replace.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/14-prohibited-space-instructions.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/15-prohibited-delete-issue.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/16-prohibited-execute-destructive.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/17-opaque-execute-write.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/18-unknown-tool-fails-closed.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/19-write-at-read-tier.json +25 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/20-high-risk-at-t3.json +19 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/21-t4-single-approver.json +13 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/22-t4-requester-self-approval.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/23-cross-tenant-target.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/24-bulk-jql-write.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/25-bulk-wildcard-write.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/26-circular-delegation.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/27-delegation-depth-exceeded.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/28-chain-does-not-end-at-origin.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/29-fabricated-completion.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/30-stale-proposal-not-expired.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/31-agent-as-decision-owner.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/32-credential-in-context.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/33-instructions-labeled-trusted.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/34-unknown-field-token.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/35-unbounded-budget.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/36-empty-do-not-do.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/37-dual-requester-whitespace-is-schema.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/38-dual-same-human-by-case.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/39-dual-requester-by-case.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/40-agent-id-labelled-human-approver.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/41-service-account-requests-write.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/42-comment-relabelled-user-supplied.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/43-approval-locator-is-comment-case-variant.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/44-approval-locator-is-tenant-url.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/45-approval-locator-typed-but-comment.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/46-bare-jql-write-target.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/47-filter-write-target.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/48-range-write-target.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/49-t4-capsule-to-analysis-agent.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/50-non-board-origin.json +11 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/51-impossible-calendar-expiry.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/52-unbounded-approval-lifetime.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/53-t4-approval-over-8h.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/54-completion-readback-wrong-target.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/55-completion-readback-by-write-tool.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/56-completion-readback-before-approval.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/57-bearer-token-value.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/59-secret-colon-form.json +10 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/60-opaque-execute-read.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/61-cross-tenant-url-in-target.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/62-decision-owner-agent-uppercase.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/63-decision-owner-agent-without-suffix.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/64-budget-tool-calls-exceeded.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/65-budget-review-rounds-exceeded.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/66-approved-but-proposed-pending-elsewhere.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/67-approval-locator-is-a-page.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/68-approval-locator-is-plain-url.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/69-approval-locator-free-text.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/69-return-to-non-delegator.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/70-delegate-back-into-chain.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/71-completed-readback-after-expiry.json +10 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/72-edit-whole-project.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/73-archive-whole-space.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/74-lookalike-tenant-host.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/75-foreign-url-host.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/76-password-with-value.json +10 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/77-readback-by-discover.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/78-readback-by-other-product-tool.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/79-readback-verifies-unknown-write.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/80-completed-mixed-before-after-expiry.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/81-completed-read-only-with-stray-readback.json +16 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/82-two-creates-one-readback.json +20 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/83-duplicate-op-id.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/84-userinfo-host-spoof.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/85-userinfo-on-real-site.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/86-bare-lookalike-host.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/87-agent-id-labelled-human-requester.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/88-create-readback-other-project.json +9 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/89-create-readback-wrong-type.json +10 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/90-bare-foreign-host.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/invalid/91-foreign-url-inside-jql.json +8 -0
- package/tests/fixtures/atlassian-case-capsule/valid/01-t1-read-incident-review.json +114 -0
- package/tests/fixtures/atlassian-case-capsule/valid/02-t3-create-remediation.json +122 -0
- package/tests/fixtures/atlassian-case-capsule/valid/03-t4-archive-superseded-runbook.json +97 -0
- package/tests/fixtures/atlassian-case-capsule/valid/04-t3-completed-with-readback.json +149 -0
- package/tests/fixtures/atlassian-case-capsule/valid/05-t1-injection-flagged-as-untrusted.json +123 -0
- package/tests/fixtures/atlassian-case-capsule/valid/06-t3-proposed-awaiting-approval.json +114 -0
- package/tests/fixtures/atlassian-case-capsule/valid/07-t3-no-go-rejected-record.json +114 -0
- package/tests/fixtures/atlassian-case-capsule/valid/08-t3-expired-record.json +122 -0
- package/tests/fixtures/atlassian-case-capsule/valid/09-t3-completed-return-to-delegator.json +150 -0
- package/tests/fixtures/atlassian-case-capsule/valid/10-t3-safety-prose-and-atlassian-named-owner.json +123 -0
- package/tests/fixtures/atlassian-case-capsule/valid/11-t1-completed-read-only-review.json +115 -0
- package/tests/fixtures/atlassian-case-capsule/valid/12-t1-query-with-dotted-literals.json +114 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/01-happy-incident-prevention.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/02-happy-control-evidence.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/03-happy-knowledge-integrity.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/04-happy-adr-superseded.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/05-happy-ai-cost.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/06-cross-incident-knowledge.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/07-cross-audit-incident.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/08-gate-create-and-publish.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/09-adv-injection-in-comment.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/10-adv-prohibited-approval.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/11-adv-bulk-delete.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/12-adv-restriction-change.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/13-ambiguous-help.json +4 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/14-unsupported-delivery-bottleneck.json +4 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/15-direct-authoring-no-specialist.json +4 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/16-draft-only-must-not-gate.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/17-adv-restriction-change-no-product-word.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/18-adv-permission-grant.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/19-adv-alert-acknowledge.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/20-adv-purge-without-product-word.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/21-adv-space-ai-instructions.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/22-adv-injection-by-issue-key.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/23-negated-write-does-not-gate.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/24-noun-change-request-not-a-write.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/25-comment-on-whether-not-a-write.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/expected/26-requested-update-gates.json +6 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/01-happy-incident-prevention.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/02-happy-control-evidence.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/03-happy-knowledge-integrity.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/04-happy-adr-superseded.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/05-happy-ai-cost.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/06-cross-incident-knowledge.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/07-cross-audit-incident.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/08-gate-create-and-publish.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/09-adv-injection-in-comment.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/10-adv-prohibited-approval.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/11-adv-bulk-delete.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/12-adv-restriction-change.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/13-ambiguous-help.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/14-unsupported-delivery-bottleneck.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/15-direct-authoring-no-specialist.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/16-draft-only-must-not-gate.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/17-adv-restriction-change-no-product-word.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/18-adv-permission-grant.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/19-adv-alert-acknowledge.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/20-adv-purge-without-product-word.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/21-adv-space-ai-instructions.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/22-adv-injection-by-issue-key.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/23-negated-write-does-not-gate.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/24-noun-change-request-not-a-write.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/25-comment-on-whether-not-a-write.json +8 -0
- package/tests/fixtures/atlassian-maestro-routing/inputs/26-requested-update-gates.json +7 -0
- package/tests/fixtures/atlassian-maestro-routing/taxonomy.json +68 -0
- package/tests/fixtures/aws-maestro-routing/expected/042-happy-dynamodb-patterns.json +6 -0
- package/tests/fixtures/aws-maestro-routing/expected/043-happy-dynamodb-vector-index.json +6 -0
- package/tests/fixtures/aws-maestro-routing/inputs/042-happy-dynamodb-patterns.json +7 -0
- package/tests/fixtures/aws-maestro-routing/inputs/043-happy-dynamodb-vector-index.json +7 -0
- package/tests/fixtures/aws-maestro-routing/taxonomy.json +15 -1
- package/tests/fixtures/azure-maestro-routing/expected/028-happy-cosmosdb-pattern-feature-plan.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/029-happy-cosmosdb-pattern-refactor.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-hot-partition-not-key-vault.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-partition-key-not-key-vault.json +6 -0
- package/tests/fixtures/azure-maestro-routing/expected/adv-cosmos-throttling-investigation.json +6 -0
- package/tests/fixtures/azure-maestro-routing/inputs/028-happy-cosmosdb-pattern-feature-plan.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/029-happy-cosmosdb-pattern-refactor.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-hot-partition-not-key-vault.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-partition-key-not-key-vault.json +7 -0
- package/tests/fixtures/azure-maestro-routing/inputs/adv-cosmos-throttling-investigation.json +7 -0
- package/tests/fixtures/azure-maestro-routing/taxonomy.json +21 -2
- package/tests/fixtures/gcp-maestro-routing/expected/049-happy-bigtable-row-key.json +6 -0
- package/tests/fixtures/gcp-maestro-routing/expected/adv-bigtable-not-firestore.json +8 -0
- package/tests/fixtures/gcp-maestro-routing/inputs/049-happy-bigtable-row-key.json +7 -0
- package/tests/fixtures/gcp-maestro-routing/inputs/adv-bigtable-not-firestore.json +7 -0
- package/tests/fixtures/gcp-maestro-routing/taxonomy.json +15 -0
- package/tests/fixtures/huawei-maestro-routing/expected/050-happy-geminidb-cassandra-partition.json +6 -0
- package/tests/fixtures/huawei-maestro-routing/expected/adv-geminidb-mongo-routes-dds.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/inputs/050-happy-geminidb-cassandra-partition.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/inputs/adv-geminidb-mongo-routes-dds.json +7 -0
- package/tests/fixtures/huawei-maestro-routing/taxonomy.json +15 -0
- package/tests/fixtures/nosql-scenarios/scenarios.json +472 -0
- package/tests/fixtures/oci-maestro-routing/expected/031-happy-nosql-database-architect.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/032-happy-nosql-global-active-table.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/033-happy-nosql-pattern-recovery.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/034-happy-nosql-pattern-refactor.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-live-mutation.json +6 -0
- package/tests/fixtures/oci-maestro-routing/expected/adv-nosql-not-autonomous.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/031-happy-nosql-database-architect.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/032-happy-nosql-global-active-table.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/033-happy-nosql-pattern-recovery.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/034-happy-nosql-pattern-refactor.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-live-mutation.json +7 -0
- package/tests/fixtures/oci-maestro-routing/inputs/adv-nosql-not-autonomous.json +7 -0
- package/tests/fixtures/oci-maestro-routing/taxonomy.json +27 -0
- package/tests/requirements-ci.txt +8 -0
- package/tests/validate-atlassian-case-capsule.py +24 -0
- package/tests/validate-aws-skill-quality.py +7 -0
- package/tests/validate-catalog.py +1 -0
- package/tests/validate-nosql-audit.py +741 -0
- package/tests/validate-nosql-operations.py +136 -0
- package/tests/validate-nosql-pattern-evals.py +96 -0
- package/tests/validate-nosql-scenarios.py +94 -0
- package/tests/validate-skill-manifest.py +6 -1
- package/tests/validate-skill-references.py +229 -0
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
interface:
|
|
2
|
+
display_name: Confluence Document Authoring
|
|
3
|
+
short_description: Templates for engineering, product, business, and support
|
|
4
|
+
default_prompt: Use $confluence-document-authoring to choose a suitable template
|
|
5
|
+
and draft clear, sourced documentation for its business, engineering, or support
|
|
6
|
+
audience.
|
|
7
|
+
icon_small: assets/icon.svg
|
|
8
|
+
icon_large: assets/icon.svg
|
|
9
|
+
policy:
|
|
10
|
+
products:
|
|
11
|
+
- chatgpt
|
|
12
|
+
- codex
|
|
13
|
+
- api
|
|
14
|
+
- atlas
|
|
15
|
+
allow_implicit_invocation: true
|
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
# Fictional example: proposed asynchronous receipt delivery
|
|
2
|
+
|
|
3
|
+
This example is invented for training. All names, requirements, and observations below belong to the fictional brief. No live system was inspected, no test was run, no Jira issue was created, and no decision was accepted. Source identifiers refer only to the self-contained brief below; there are no external links.
|
|
4
|
+
|
|
5
|
+
## Fictional brief and evidence register
|
|
6
|
+
|
|
7
|
+
| Source ID | Supplied fictional information | What it establishes | What it does not establish |
|
|
8
|
+
| --- | --- | --- | --- |
|
|
9
|
+
| F1 | The team describes a checkout handler that calls an email provider before returning the receipt response. | The reported current sequence. | Actual latency, provider reliability, or verified production behavior. |
|
|
10
|
+
| F2 | The product lead asks that an email-provider outage not prevent a completed purchase from being acknowledged to the buyer. | A requested business outcome. | An approved latency target or delivery-time commitment. |
|
|
11
|
+
| F3 | The platform owner says the team can operate a background worker and a durable database table. | A stated operational capability. | Measured capacity, safe retention limits, or an implemented design. |
|
|
12
|
+
| F4 | The operations lead reports that buyers sometimes contact support about missing receipts. | A reported support concern. | Frequency, cause, or proof that the proposed design will reduce contacts. |
|
|
13
|
+
| F5 | The architecture review chair has been asked to decide this change; no review result has been supplied. | The intended decision authority and missing outcome. | Acceptance, rejection, or authorization to deploy. |
|
|
14
|
+
| F6 | The receipt-service team is preparing this proposal; Mira is the service owner in this fictional brief. | The draft authoring team and recorded service ownership. | Authority to accept the architectural decision. |
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
# ADR-004: Decouple receipt email delivery from checkout acknowledgement
|
|
19
|
+
|
|
20
|
+
| Metadata | Value |
|
|
21
|
+
| --- | --- |
|
|
22
|
+
| Status | Proposed |
|
|
23
|
+
| Author / owner | Fictional receipt-service team / Mira, service owner |
|
|
24
|
+
| Document version | 0.1 — initial proposal |
|
|
25
|
+
| Decision authority | Architecture review chair, as stated in F5; authority confirmation pending |
|
|
26
|
+
| Decision date | Not decided |
|
|
27
|
+
| Jira reference | Not linked; no issue exists in this example |
|
|
28
|
+
| Supersedes | None |
|
|
29
|
+
| Superseded by | None |
|
|
30
|
+
|
|
31
|
+
## Decision to make
|
|
32
|
+
|
|
33
|
+
Should checkout record a receipt-delivery request for a worker to process after the purchase is committed, instead of waiting for the email provider before acknowledging checkout?
|
|
34
|
+
|
|
35
|
+
## Context and drivers
|
|
36
|
+
|
|
37
|
+
F1 reports that checkout currently waits for the email provider. F2 requests that a provider outage not block acknowledgement of a completed purchase. These statements motivate investigating separation of the two operations; they do not establish an incident rate or a performance improvement.
|
|
38
|
+
|
|
39
|
+
F3 suggests the team could operate a worker and a database-backed queue. That capability is a team report and still needs a concrete capacity and failure-recovery check. F4 makes delivery visibility relevant, but the cause of reported missing receipts remains unknown.
|
|
40
|
+
|
|
41
|
+
## Options considered
|
|
42
|
+
|
|
43
|
+
| Option | Expected benefit | Cost / risk | Evidence or uncertainty |
|
|
44
|
+
| --- | --- | --- | --- |
|
|
45
|
+
| Keep synchronous delivery | Preserves the reported sequence and avoids a new worker. | Checkout acknowledgement remains coupled to the provider call. | Sequence is reported in F1; actual failure behavior is unverified. |
|
|
46
|
+
| Store a delivery request with the purchase, then process it asynchronously | Could separate purchase acknowledgement from provider availability and retain delivery work. | Requires worker ownership, retry rules, backlog monitoring, and handling of repeated delivery attempts. | F3 reports relevant capability; transaction boundaries and capacity are unverified. |
|
|
47
|
+
| Commit the purchase, then send a transient event | Could separate response handling from delivery with less persistent state. | An event publication failure after commit could leave delivery work unrecorded unless another mechanism closes that gap. | This failure window is design reasoning; no implementation or test result is supplied. |
|
|
48
|
+
|
|
49
|
+
## Proposed decision
|
|
50
|
+
|
|
51
|
+
Propose recording a receipt-delivery request in the same transaction as the completed purchase, with a worker processing pending requests. This is a recommendation for review, not an accepted decision or a deployment instruction.
|
|
52
|
+
|
|
53
|
+
The proposal prioritizes retaining delivery intent when the provider is unavailable. Its main unresolved tradeoff is the balance between retrying uncertain deliveries and avoiding duplicate emails. A worker may lose its response after the provider accepts a message; retrying could then send another copy. The provider's deduplication capabilities have not been established.
|
|
54
|
+
|
|
55
|
+
## Consequences
|
|
56
|
+
|
|
57
|
+
| Kind | Expected consequence | Required follow-up |
|
|
58
|
+
| --- | --- | --- |
|
|
59
|
+
| Positive | Checkout could acknowledge a committed purchase independently of the provider call. | Verify the transaction and response paths against F2. |
|
|
60
|
+
| Negative | The service gains background work, a backlog, and a new operational responsibility. | Define ownership, capacity checks, alert signals, and a recovery runbook. |
|
|
61
|
+
| Negative | An uncertain provider outcome may lead to duplicate receipt attempts. | Verify provider behavior and agree the business tolerance before acceptance. |
|
|
62
|
+
| Follow-on | Support needs a way to distinguish pending, delivered, and unresolved receipts. | Define observable delivery states without equating an attempted send with confirmed receipt. |
|
|
63
|
+
|
|
64
|
+
## Decision authority and evidence
|
|
65
|
+
|
|
66
|
+
No acceptance evidence is available. F5 identifies the intended review chair but supplies no decision record. The status remains **Proposed**. No acceptance timestamp or accepted version is recorded.
|
|
67
|
+
|
|
68
|
+
## Validation and follow-up
|
|
69
|
+
|
|
70
|
+
| Question / action | Proposed owner | Evidence needed | Due / tracking |
|
|
71
|
+
| --- | --- | --- | --- |
|
|
72
|
+
| Can purchase and delivery intent commit atomically? | Receipt-service owner | Reviewed transaction design and a failure-focused test. | Not set / not linked |
|
|
73
|
+
| Can the provider deduplicate repeated attempts? | Integration owner, assignment pending | Provider contract and a controlled test of uncertain responses. | Not set / not linked |
|
|
74
|
+
| What delivery delay and duplicate rate are acceptable? | Product lead | Explicit business decision with rationale. | Not set / not linked |
|
|
75
|
+
| Can the worker recover an accumulated backlog safely? | Platform owner | Capacity experiment, monitoring proposal, and recovery walkthrough. | Not set / not linked |
|
|
76
|
+
|
|
77
|
+
## Uncertainty and lifecycle
|
|
78
|
+
|
|
79
|
+
No production measurements, provider contract, schema, endpoint specification, or completed tests were supplied. No quantitative benefit is claimed. The proposal may change if atomic persistence is infeasible or the retry tradeoff cannot meet an agreed business requirement.
|
|
80
|
+
|
|
81
|
+
If this ADR is later accepted, record the actual authority, evidence, date, and accepted version. A later substantive reversal should use a new ADR with reciprocal superseding references; retain this record's original rationale.
|
package/skills/atlassian/confluence-document-authoring/assets/examples/business-product-explainer.md
ADDED
|
@@ -0,0 +1,99 @@
|
|
|
1
|
+
# Service Request Hub: a business product explainer
|
|
2
|
+
|
|
3
|
+
> **Synthetic example.** The product and source extracts below are fictional teaching material. They describe a proposal, not a real product, customer finding, release, test result, or commitment. No measured benefit or availability claim is established.
|
|
4
|
+
|
|
5
|
+
| Metadata | Value |
|
|
6
|
+
|---|---|
|
|
7
|
+
| Audience / purpose | Business operations, request reviewers, and support; explain the proposed product in familiar language |
|
|
8
|
+
| Accountable owner / reviewer | unknown / unknown |
|
|
9
|
+
| Document lifecycle / review trigger | draft / review when product behavior, eligibility, or commercial evidence becomes available |
|
|
10
|
+
| Revision / last reviewed | example revision A / unknown |
|
|
11
|
+
| Sources / revisions / dates | Synthetic proposal S1, revision A, date unknown; synthetic process note S2, revision A, date unknown; extracts below |
|
|
12
|
+
| Product / version / availability | Service Request Hub / unknown / unknown |
|
|
13
|
+
| Jira / related documentation | unknown / unknown; no live issue or page is represented |
|
|
14
|
+
|
|
15
|
+
## What it would do
|
|
16
|
+
|
|
17
|
+
Service Request Hub is a proposed shared place for employees to submit service requests and see their progress. Reviewers would use the same request record to understand the need, ask for details, and record an outcome. These are intended behaviors in the synthetic proposal, not verified product capabilities. [S1](#s1-synthetic-product-proposal)
|
|
18
|
+
|
|
19
|
+
## Who it would help and why
|
|
20
|
+
|
|
21
|
+
The intended users are employees requesting an internal service and the people who review those requests. The synthetic process note reports that requests arrive by email and reviewers keep a separate tracking list. It also reports that requesters ask reviewers for updates. These are fictional reported observations; their frequency and cost are unknown. [S2](#s2-synthetic-process-note)
|
|
22
|
+
|
|
23
|
+
| Before, as reported in the synthetic note | Proposed workflow | Evidence state |
|
|
24
|
+
|---|---|---|
|
|
25
|
+
| A requester emails a service team and later asks for an update. | The requester submits a request and views its recorded status in one place. | Reported problem; proposed behavior; no implementation evidence |
|
|
26
|
+
| A reviewer copies request details into a tracking list. | The reviewer works from the submitted request record. | Reported process; proposed behavior; no observed time saving |
|
|
27
|
+
| Missing details require another message. | The reviewer asks for clarification on the existing request. | Proposed interaction; notification behavior and exact controls are unknown |
|
|
28
|
+
|
|
29
|
+
The value proposition is easier coordination and clearer progress. A reduction in handling time is a desired outcome, not a measured result.
|
|
30
|
+
|
|
31
|
+
| Intended benefit | What would demonstrate it | Current evidence |
|
|
32
|
+
|---|---|---|
|
|
33
|
+
| Requesters can understand progress without asking for a separate update. | Proposed measurement: compare status-related follow-up contacts for a defined request population and period. | Not measured; baseline, target, and measurement owner unknown |
|
|
34
|
+
| Reviewers avoid copying the same information into a separate list. | Proposed measurement: observe whether the end-to-end workflow still requires duplicate entry. | Not measured; no workflow study supplied |
|
|
35
|
+
| Requests remain understandable when a reviewer changes. | Proposed check: an authorized replacement reviewer can identify the request, outstanding information, and recorded outcome. | Not verified; permission and handover behavior unknown |
|
|
36
|
+
|
|
37
|
+
## Key terms in business language
|
|
38
|
+
|
|
39
|
+
These working definitions come from the synthetic proposal. They remain proposed product vocabulary. [S1](#s1-synthetic-product-proposal)
|
|
40
|
+
|
|
41
|
+
| Term | Business meaning | Illustrative example |
|
|
42
|
+
|---|---|---|
|
|
43
|
+
| Request | One recorded need that someone asks a service team to handle. | An employee asks for access to a reporting tool. |
|
|
44
|
+
| Queue | A list of requests that a team needs to review or handle. | A service reviewer opens the list of requests awaiting attention. |
|
|
45
|
+
| Assigned reviewer | The person currently responsible for evaluating a request. | A reviewer checks whether the request contains enough information. |
|
|
46
|
+
| Status | A visible description of where a request is in the process. | “Needs clarification” would mean the reviewer requires more information; the exact product label is unverified. |
|
|
47
|
+
| Outcome | The recorded result of a request review. | The request is completed or declined with an explanation; permitted outcomes remain to be defined. |
|
|
48
|
+
|
|
49
|
+
## Proposed workflow
|
|
50
|
+
|
|
51
|
+
This is a conceptual journey, not a tested how-to. Exact interface labels, permissions, and supported transitions are unknown.
|
|
52
|
+
|
|
53
|
+
| Step | Intended action | Intended result | Open question |
|
|
54
|
+
|---|---|---|---|
|
|
55
|
+
| 1 | An employee submits the service need and relevant context. | A request record is available for review. | Which fields and supporting materials are required? |
|
|
56
|
+
| 2 | A reviewer checks the request. | The reviewer can continue evaluation or ask for missing information. | How is a reviewer assigned, and which requests may they view? |
|
|
57
|
+
| 3 | The employee provides clarification when requested. | The updated information remains associated with the same request. | Are notifications supported, and what happens if no response arrives? |
|
|
58
|
+
| 4 | The reviewer records an outcome. | The requester can understand the result and any next action. | What outcomes are allowed, and can a closed request be reopened? |
|
|
59
|
+
|
|
60
|
+
## Capabilities and boundaries
|
|
61
|
+
|
|
62
|
+
| Business need | Proposed capability | Boundary or missing evidence |
|
|
63
|
+
|---|---|---|
|
|
64
|
+
| Give teams a shared request record. | Capture request details and progress. | Storage, retention, search, and actual implementation are unknown. |
|
|
65
|
+
| Clarify incomplete requests. | Keep clarification associated with the request. | Attachments, notification channels, and audit history are unknown. |
|
|
66
|
+
| Explain the current state to requesters. | Show a meaningful status and recorded outcome. | Accessibility and customer-visible wording have not been validated. |
|
|
67
|
+
| Complete the underlying service. | Outside the current proposal's described scope. | Recording an outcome does not prove that an external service action occurred. |
|
|
68
|
+
|
|
69
|
+
## Availability, prerequisites, and commercial terms
|
|
70
|
+
|
|
71
|
+
| Question | Answer based on the example evidence |
|
|
72
|
+
|---|---|
|
|
73
|
+
| Can employees use it today? | Unknown. No release, deployment, or enablement evidence is supplied. |
|
|
74
|
+
| Who will be eligible? | The intended users are employees and reviewers. Actual plans, regions, cohorts, and permissions are unknown. |
|
|
75
|
+
| What setup is required? | Unknown. The proposal implies requester and reviewer roles, but does not establish configuration or identity prerequisites. |
|
|
76
|
+
| What does it cost? | Unknown. No pricing, licensing, or contract source is supplied. |
|
|
77
|
+
| What support or service commitments apply? | Unknown. No support terms, service targets, or contractual commitments are supplied. |
|
|
78
|
+
|
|
79
|
+
## Questions and help
|
|
80
|
+
|
|
81
|
+
**Does this replace the team’s service work?** The proposal describes coordination of requests. It does not establish automated fulfillment or integration with service systems. [S1](#s1-synthetic-product-proposal)
|
|
82
|
+
|
|
83
|
+
**Will this save time?** That is a desired benefit. There is no baseline, measured result, or validated forecast in the example evidence.
|
|
84
|
+
|
|
85
|
+
**Where can I get help or submit feedback?** Unknown. A real publication needs a verified support route and accountable owner.
|
|
86
|
+
|
|
87
|
+
## Optional technical appendix
|
|
88
|
+
|
|
89
|
+
Architecture, integration contracts, permission model, and data retention rules are unknown. A technical design should answer those questions before this proposal is used as implementation or procurement guidance. No architecture is inferred from the business description.
|
|
90
|
+
|
|
91
|
+
## Synthetic source extracts
|
|
92
|
+
|
|
93
|
+
### S1: Synthetic product proposal
|
|
94
|
+
|
|
95
|
+
Revision A; date unknown; authority and approval unknown. Proposed scope: employees submit requests; reviewers inspect a shared request record, seek clarification, and record an outcome; requesters can view progress. Working terms: request, queue, assigned reviewer, status, outcome. Fulfillment automation is not described. No release, entitlement, interface, pricing, or service commitments are supplied.
|
|
96
|
+
|
|
97
|
+
### S2: Synthetic process note
|
|
98
|
+
|
|
99
|
+
Revision A; date unknown; fictional reported observations only: requests arrive by email, reviewers maintain a separate list, and requesters ask for updates. No sample size, elapsed-time measurement, customer quotation, or validated research result is supplied.
|
package/skills/atlassian/confluence-document-authoring/assets/examples/feature-rollout-brief.md
ADDED
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Feature overview and rollout brief: request clarification
|
|
2
|
+
|
|
3
|
+
> **Synthetic example.** All product descriptions and source extracts below are fictional teaching material. This is a proposed feature brief. Implementation, deployment, customer availability, approval, and measured results are unknown.
|
|
4
|
+
|
|
5
|
+
| Metadata | Value |
|
|
6
|
+
|---|---|
|
|
7
|
+
| Audience / purpose | Business operations, support, product, and engineering; explain the intended behavior and unresolved rollout conditions |
|
|
8
|
+
| Accountable owner / reviewer | unknown / unknown |
|
|
9
|
+
| Document lifecycle / review trigger | draft / review after behavior, permission, and availability evidence is supplied |
|
|
10
|
+
| Revision / last reviewed | example revision A / unknown |
|
|
11
|
+
| Sources / revisions / dates | Synthetic requirement S1 and process note S2, revision A, dates unknown; extracts below |
|
|
12
|
+
| Product / version / availability | Service Request Hub / unknown / unknown |
|
|
13
|
+
| Jira / PRD / design / related docs | unknown / unknown / unknown / unknown; no live records are represented |
|
|
14
|
+
|
|
15
|
+
## Existing problem
|
|
16
|
+
|
|
17
|
+
The synthetic process note reports that reviewers ask for missing request details outside the request record. This may make it harder to see which information is outstanding. The note does not establish how often this happens or whether it delays fulfillment; those effects remain hypotheses. [S2](#s2-synthetic-process-note)
|
|
18
|
+
|
|
19
|
+
## What would change
|
|
20
|
+
|
|
21
|
+
The proposed feature would let a reviewer return a request for clarification, explain what is missing, and receive the requester’s response on the same record. [S1](#s1-synthetic-draft-requirement)
|
|
22
|
+
|
|
23
|
+
| Situation | Reported current process | Proposed behavior | Delivery state |
|
|
24
|
+
|---|---|---|---|
|
|
25
|
+
| A reviewer needs more information. | The reviewer sends a separate message. | The reviewer records a clarification request on the existing request. | Proposed; implementation unknown |
|
|
26
|
+
| The requester supplies the missing information. | The response may be separated from the tracking record. | The response remains associated with the same request and is available for review. | Proposed; implementation unknown |
|
|
27
|
+
| Another reviewer checks progress. | They may need to locate the separate exchange. | An authorized reviewer can see the outstanding clarification and response. | Proposed; authorization behavior unknown |
|
|
28
|
+
|
|
29
|
+
**Desired value:** Keep the request and its clarification together so both parties can understand what is needed next. **Measured value:** Not measured; no baseline, target, experiment, or result is supplied.
|
|
30
|
+
|
|
31
|
+
The proposal does not define automated reminders, new attachment support, external messaging integration, or automatic completion of the underlying service. Those capabilities must not be implied.
|
|
32
|
+
|
|
33
|
+
## Availability and eligibility
|
|
34
|
+
|
|
35
|
+
| Dimension | Verified state | Proposed intent / unresolved detail |
|
|
36
|
+
|---|---|---|
|
|
37
|
+
| Implemented behavior | Unknown | The draft describes behavior but supplies no code or verification record. |
|
|
38
|
+
| Product version / environment | Unknown | No release or deployment source is supplied. |
|
|
39
|
+
| User enablement / cohort | Unknown | No feature-enable record or cohort decision is supplied. |
|
|
40
|
+
| Roles / permissions | Unknown | Intended participants are the requester and an authorized reviewer; exact permission rules need a source. |
|
|
41
|
+
| Plan / region / commercial eligibility | Unknown | No entitlement source is supplied. |
|
|
42
|
+
| Rollout date | Unknown | No authorized schedule is supplied. |
|
|
43
|
+
|
|
44
|
+
This brief can support discussion of the proposal. It cannot support a customer announcement that the feature is available.
|
|
45
|
+
|
|
46
|
+
## Proposed user journey
|
|
47
|
+
|
|
48
|
+
The following actions describe intent; they are not verified interface instructions. Menu labels, controls, and screenshots are unknown.
|
|
49
|
+
|
|
50
|
+
| Step | Intended action | Intended result | Failure or boundary question |
|
|
51
|
+
|---|---|---|---|
|
|
52
|
+
| 1 | The reviewer identifies the missing information and asks for clarification. | The explanation is associated with the existing request. | Must the explanation contain text? What happens if saving fails? |
|
|
53
|
+
| 2 | The requester opens the request and reads the clarification. | The requester understands what to provide. | How will the requester learn that clarification was requested? |
|
|
54
|
+
| 3 | The requester supplies the missing information. | The response remains on the same request and is available for review. | What happens if the request was closed or reassigned in the meantime? |
|
|
55
|
+
| 4 | The reviewer continues the review. | The reviewer can assess the new information in context. | Which state transitions and reviewers are permitted? |
|
|
56
|
+
|
|
57
|
+
## Illustrative scenarios
|
|
58
|
+
|
|
59
|
+
These examples clarify intended behavior; none is an executed test.
|
|
60
|
+
|
|
61
|
+
| Scenario | Starting condition | Proposed result | Unresolved rule |
|
|
62
|
+
|---|---|---|---|
|
|
63
|
+
| Ordinary clarification | A fictional access request omits the reason access is needed. | The reviewer asks for that reason, and the requester replies on the same record. | Required fields and permission checks are unknown. |
|
|
64
|
+
| Reassignment | The original reviewer changes while clarification is outstanding. | An authorized replacement reviewer should be able to continue the work. | Visibility, assignment, and notification semantics are unknown. |
|
|
65
|
+
| Closed request | A requester attempts to respond after an outcome was recorded. | Unknown; the draft does not define this transition. | Product must establish whether to reject, reopen, or use another supported path. |
|
|
66
|
+
| Repeated submission | A requester is unsure whether a response was saved and submits again. | Unknown; duplicate handling is not specified. | Engineering and product need an observable rule and verification evidence. |
|
|
67
|
+
|
|
68
|
+
## Limits and compatibility
|
|
69
|
+
|
|
70
|
+
Existing request visibility must be understood before claiming that clarification is visible to another person. Compatibility with historical requests, concurrent edits, existing integrations, attachments, and assistive technologies is unknown. No migration or retention behavior is established by the proposal.
|
|
71
|
+
|
|
72
|
+
## Proposed rollout preparation
|
|
73
|
+
|
|
74
|
+
These are proposed readiness questions, not approved gates or completed checks. Decision authority and assignments are unknown.
|
|
75
|
+
|
|
76
|
+
| Question to resolve | Evidence needed | Owner | Current state |
|
|
77
|
+
|---|---|---|---|
|
|
78
|
+
| Does the intended interaction work for the target users? | A versioned behavior demonstration or verification record covering the normal path and agreed boundaries | unknown | Not verified |
|
|
79
|
+
| Does clarification preserve the intended access boundaries? | Agreed permission rules and evidence for authorized and unauthorized cases | unknown | Unknown |
|
|
80
|
+
| Which users may receive the feature? | Approved eligibility and enablement decision with actual configuration evidence when enabled | unknown | Unknown |
|
|
81
|
+
| Can the feature be disabled safely? | Reviewed recovery procedure covering in-progress clarification, persisted data, and user-visible effects | unknown | Unknown |
|
|
82
|
+
| Can support identify and resolve expected questions? | Reviewed customer-safe article, escalation route, and troubleshooting evidence | unknown | Unknown |
|
|
83
|
+
|
|
84
|
+
No live rollout action is part of this brief. Enablement procedure, recovery procedure, stop criteria, support route, and release-note links remain unknown.
|
|
85
|
+
|
|
86
|
+
## Proposed measurement
|
|
87
|
+
|
|
88
|
+
One candidate question is whether requesters and reviewers can identify the outstanding clarification from the request alone. A proposed evaluation would observe that task in an agreed sample and record failure modes. A separate operational measure could count clarification-related contacts outside the request record for a defined population and period. Both approaches need an owner, baseline, measurement definition, and agreed interpretation; no target or result is invented here.
|
|
89
|
+
|
|
90
|
+
## Decisions and next communication
|
|
91
|
+
|
|
92
|
+
| Open decision | Why it matters | Owner / due | Evidence needed to close |
|
|
93
|
+
|---|---|---|---|
|
|
94
|
+
| Allowed transitions and closed-request behavior | Determines whether the instructions and recovery paths are correct | unknown / unknown | Versioned product rule and decision authority |
|
|
95
|
+
| Eligibility and enablement | Determines who can be told to use the feature | unknown / unknown | Actual availability evidence for the stated audience |
|
|
96
|
+
| Notifications and support routing | Determines how users discover and resolve pending clarification | unknown / unknown | Agreed behavior and verified support references |
|
|
97
|
+
|
|
98
|
+
A customer-facing announcement should be prepared from verified availability and instructions when those sources exist. No announcement date, approval, or delivery result is established in this example.
|
|
99
|
+
|
|
100
|
+
## Synthetic source extracts
|
|
101
|
+
|
|
102
|
+
### S1: Synthetic draft requirement
|
|
103
|
+
|
|
104
|
+
Revision A; date unknown; author and approval unknown. Proposed behavior: a reviewer can ask for missing information on an existing request; the requester can respond on the same record; an authorized reviewer can continue review using that response. No implementation state, exact labels, permission contract, notification behavior, rollout schedule, recovery procedure, or commercial eligibility is supplied.
|
|
105
|
+
|
|
106
|
+
### S2: Synthetic process note
|
|
107
|
+
|
|
108
|
+
Revision A; date unknown. Fictional reported process: reviewers sometimes ask for missing information outside the request record. Frequency, delay, customer impact, and the affected product version are unknown. No observed study or measured result is supplied.
|
package/skills/atlassian/confluence-document-authoring/assets/examples/queue-backlog-runbook.md
ADDED
|
@@ -0,0 +1,158 @@
|
|
|
1
|
+
# SYNTHETIC runbook: investigate a growing queue backlog
|
|
2
|
+
|
|
3
|
+
**SYNTHETIC EXAMPLE — NOT EXECUTED.** The observations below are invented to demonstrate an evidence-based investigation. They are not output from a cluster. Commands are read-only examples with unresolved target placeholders; no cluster access, recovery action, or operational validation has occurred.
|
|
4
|
+
|
|
5
|
+
| Metadata | Value |
|
|
6
|
+
|---|---|
|
|
7
|
+
| Document lifecycle | draft |
|
|
8
|
+
| Operational owner | unknown |
|
|
9
|
+
| Reviewer | unknown |
|
|
10
|
+
| Revision / date | synthetic revision 0.1 / unknown |
|
|
11
|
+
| Sources | Invented observations SIM-01 through SIM-04; official kubectl references below |
|
|
12
|
+
| Jira / related documentation | unknown / unknown |
|
|
13
|
+
| Review trigger | Worker rollout, queue contract change, incident learning, or completed recovery review |
|
|
14
|
+
| Procedure validation state | NOT RUN |
|
|
15
|
+
|
|
16
|
+
The lifecycle is document review status, not Confluence publication or evidence of successful execution.
|
|
17
|
+
|
|
18
|
+
## Purpose and scope
|
|
19
|
+
|
|
20
|
+
Determine whether queue growth is associated with unavailable workers, downstream throttling, an ingress increase, or an unresolved measurement gap. The runbook stops at a bounded diagnosis and recovery handoff; it does not authorize changing replicas, queue contents, deployment versions, or processing concurrency.
|
|
21
|
+
|
|
22
|
+
Synthetic impact: jobs are waiting longer. Actual customer impact, severity, processing deadline, queue provider, worker version, and service-level objective are **unknown**.
|
|
23
|
+
|
|
24
|
+
## Preconditions and exact target
|
|
25
|
+
|
|
26
|
+
| Required input | Value | Verification source / state |
|
|
27
|
+
|---|---|---|
|
|
28
|
+
| Approved environment / account | {{environment_and_account}} | {{inventory_or_incident_reference}}; NOT CHECKED |
|
|
29
|
+
| Kubeconfig context / expected API endpoint | {{kube_context}} / {{expected_api_endpoint}} | {{approved_inventory_reference}}; NOT CHECKED |
|
|
30
|
+
| Namespace / deployment | {{namespace}} / {{worker_deployment}} | {{service_inventory_reference}}; NOT CHECKED |
|
|
31
|
+
| Worker selector | {{worker_selector}} | Must match the deployment's selector and verified pod ownership; NOT CHECKED |
|
|
32
|
+
| Worker pod / ReplicaSet / container | {{worker_pod}} / {{worker_replicaset}} / {{worker_container}} | Select only from verified workload ownership; NOT CHECKED |
|
|
33
|
+
| Queue identity and metrics | {{queue_name}} / {{metrics_dashboard_url}} | {{queue_mapping_and_metric_definition_source}}; NOT CHECKED |
|
|
34
|
+
| Minimum access | Read the target deployment, ReplicaSet, pods, events, and selected pod logs | {{access_evidence}}; NOT CHECKED |
|
|
35
|
+
| Operator / incident authority | {{operator_and_authorized_read_scope}} | {{task_or_incident_reference}}; unknown |
|
|
36
|
+
| kubectl / cluster versions | {{client_and_server_versions}} | Compatibility not verified |
|
|
37
|
+
|
|
38
|
+
Resolve all placeholders before adapting the commands. Do not treat a context name, matching label, or `Running` pod phase alone as proof of correct target or healthy processing. Read bounded, redacted diagnostics; do not paste credentials or full sensitive payloads into the incident record.
|
|
39
|
+
|
|
40
|
+
## Stop conditions
|
|
41
|
+
|
|
42
|
+
Stop the affected investigation branch if the endpoint or workload identity differs from the approved inventory, access is denied, selected pods belong to another workload, the queue-to-worker mapping is unknown, or evidence is stale or contradictory. Do not infer an SLO breach or incident severity without its threshold and source. Recovery steps remain gated until their exact target, authority, procedure, and reversal limits are established.
|
|
43
|
+
|
|
44
|
+
## Procedure
|
|
45
|
+
|
|
46
|
+
| Step | Action | Expected observation | If different |
|
|
47
|
+
|---|---|---|---|
|
|
48
|
+
| 1 | Read-only: inspect the selected context's endpoint using command A. | Endpoint matches the independently approved target. | Stop; resolve the inventory/context mismatch. |
|
|
49
|
+
| 2 | Read-only: inspect deployment, selector, pods, and ReplicaSet ownership using commands B–E. | Generation is observed; ownership chain points to the intended deployment; readiness can be assessed. | Branch to workload identity or availability investigation. Do not count unrelated pods as capacity. |
|
|
50
|
+
| 3 | Read-only: record queue depth, oldest age, arrivals, completions, metric definitions, and timestamps from the verified dashboard. | Metrics refer to the same queue and interval; the direction of backlog growth can be explained. | Treat telemetry as incomplete; do not calculate a drain estimate from incomparable rates. |
|
|
51
|
+
| 4 | Read-only: inspect bounded events and logs for the verified pod/container using commands F–G. | Evidence can support or contradict unavailable-worker and downstream-failure hypotheses. | Record unavailable evidence or contradictory results; avoid assuming absence of log entries means no failure. |
|
|
52
|
+
| 5 | Compare evidence against the branch table below. | A bounded next check or escalation is selected, with remaining uncertainty explicit. | Keep multiple hypotheses open and collect the missing discriminating evidence. |
|
|
53
|
+
| 6 | Record target, evidence window, hypotheses, and required recovery owner. | Another operator can reproduce the reasoning and understand what has not been done. | Keep the investigation open; do not label the queue recovered. |
|
|
54
|
+
|
|
55
|
+
### Read-only command examples — NOT RUN
|
|
56
|
+
|
|
57
|
+
These commands follow the referenced kubectl syntax. They have not been executed or validated against a target version. Missing output fields are **unknown**, not automatically zero.
|
|
58
|
+
|
|
59
|
+
**A — selected context endpoint only:**
|
|
60
|
+
|
|
61
|
+
```sh
|
|
62
|
+
kubectl --context="{{kube_context}}" config view --minify -o jsonpath='{.clusters[0].cluster.server}'
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
**B — deployment identity and observed generation:**
|
|
66
|
+
|
|
67
|
+
```sh
|
|
68
|
+
kubectl --context="{{kube_context}}" --namespace="{{namespace}}" get deployment "{{worker_deployment}}" -o custom-columns='NAME:.metadata.name,UID:.metadata.uid,GENERATION:.metadata.generation,OBSERVED:.status.observedGeneration,DESIRED:.spec.replicas,READY:.status.readyReplicas,AVAILABLE:.status.availableReplicas,UPDATED:.status.updatedReplicas'
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
**C — deployment selector to compare with the supplied selector:**
|
|
72
|
+
|
|
73
|
+
```sh
|
|
74
|
+
kubectl --context="{{kube_context}}" --namespace="{{namespace}}" get deployment "{{worker_deployment}}" -o jsonpath='{.spec.selector}'
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
**D — selected pods and their owners:**
|
|
78
|
+
|
|
79
|
+
```sh
|
|
80
|
+
kubectl --context="{{kube_context}}" --namespace="{{namespace}}" get pods --selector="{{worker_selector}}" -o custom-columns='NAME:.metadata.name,OWNER_KIND:.metadata.ownerReferences[0].kind,OWNER:.metadata.ownerReferences[0].name,READY:.status.containerStatuses[*].ready,RESTARTS:.status.containerStatuses[*].restartCount,PHASE:.status.phase'
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
**E — ReplicaSet owner must match the deployment name and UID from B:**
|
|
84
|
+
|
|
85
|
+
```sh
|
|
86
|
+
kubectl --context="{{kube_context}}" --namespace="{{namespace}}" get replicaset "{{worker_replicaset}}" -o custom-columns='NAME:.metadata.name,OWNER_KIND:.metadata.ownerReferences[0].kind,OWNER:.metadata.ownerReferences[0].name,OWNER_UID:.metadata.ownerReferences[0].uid'
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
Repeat the ownership check for each distinct ReplicaSet before treating all selected pods as part of the deployment. Confirm the controller owner if multiple owner references are present.
|
|
90
|
+
|
|
91
|
+
**F — events for one verified worker pod:**
|
|
92
|
+
|
|
93
|
+
```sh
|
|
94
|
+
kubectl --context="{{kube_context}}" --namespace="{{namespace}}" get events --field-selector="involvedObject.name={{worker_pod}}" --sort-by='.metadata.creationTimestamp'
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
**G — bounded logs for one verified container:**
|
|
98
|
+
|
|
99
|
+
```sh
|
|
100
|
+
kubectl --context="{{kube_context}}" --namespace="{{namespace}}" logs "{{worker_pod}}" --container="{{worker_container}}" --since=10m --tail=200 --limit-bytes=65536 --timestamps=true
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
Record the returned event object's identity and time window; a reused pod name or an empty event list is not proof that no incident occurred. Log sampling is bounded and may omit relevant events.
|
|
104
|
+
|
|
105
|
+
## Invented observations for this worked example
|
|
106
|
+
|
|
107
|
+
**Every entry in this section is simulated.** It does not populate the real execution evidence record.
|
|
108
|
+
|
|
109
|
+
| ID | Synthetic observation | Interpretation / limitation |
|
|
110
|
+
|---|---|---|
|
|
111
|
+
| SIM-01 | Four desired workers; four ready and available; observed generation matches the deployment generation; sampled pod ownership matches. | No unavailability is shown in this snapshot. Readiness alone does not demonstrate completed jobs. |
|
|
112
|
+
| SIM-02 | Queue depth rises from 1,200 at 10:00 to 5,700 at 10:05 to 10,200 at 10:10 in a fictional observation window. | The simulated average increase is 15 jobs/second. Actual metric definitions remain unverified. |
|
|
113
|
+
| SIM-03 | Simulated arrival rate is 20 jobs/second and completion rate is 5 jobs/second throughout that window. | Their difference is consistent with SIM-02 under the scenario's simple queue accounting assumption; it is not a measured production rate. |
|
|
114
|
+
| SIM-04 | Two sampled worker containers show downstream HTTP `429` responses during the same window; no restarts appear in the sampled pod status. | Throttling is a plausible contributor. The scope, authoritative retry contract, and causal effect remain unknown. |
|
|
115
|
+
|
|
116
|
+
For the synthetic rates only, 20 arrivals minus 5 completions equals 15 additional jobs per second, or 4,500 jobs per five minutes. A drain-time claim would be unjustified while completions remain below arrivals. The actual rates and any recovery estimate require real observations and consistent metric definitions.
|
|
117
|
+
|
|
118
|
+
## Evidence branches
|
|
119
|
+
|
|
120
|
+
| Evidence | Working hypothesis | Next discriminating check | Recovery implication |
|
|
121
|
+
|---|---|---|---|
|
|
122
|
+
| Ready/available replicas below the intended baseline, with matching ownership and recent warning events | Worker availability may limit throughput. | Check scheduling, readiness failure, image/startup errors, and active rollout evidence. | Use a reviewed workload recovery procedure only after identifying the failure; none is supplied here. |
|
|
123
|
+
| Workers appear available; downstream `429` responses coincide with low completions | A downstream limit may constrain useful work. | Obtain the actual downstream rate-limit scope, `Retry-After` behavior, worker retry policy, and request-rate telemetry. | Increasing worker replicas could increase rejected traffic. A reviewed concurrency or admission change may be appropriate, but is not authorized by this example. |
|
|
124
|
+
| Arrival rate increases while completion rate remains near a verified baseline | Ingress may exceed processing capacity. | Compare arrivals and completions over matching windows; verify per-tenant distribution and agreed capacity limits. | Capacity or admission decisions need measured limits and service-owner authority. |
|
|
125
|
+
| Dashboard identity, metric definitions, or queue mapping is missing | Diagnosis remains unknown. | Resolve the telemetry mapping before relying on the trend. | No recovery command follows from ambiguous metrics. |
|
|
126
|
+
|
|
127
|
+
**Synthetic working conclusion:** downstream throttling is a supported hypothesis to investigate next. It is not a confirmed root cause, and no recovery is demonstrated.
|
|
128
|
+
|
|
129
|
+
## Recovery / rollback handoff
|
|
130
|
+
|
|
131
|
+
| Candidate situation | Required procedure and authority | Reversal / data constraints | Current state |
|
|
132
|
+
|---|---|---|---|
|
|
133
|
+
| Downstream throttling is confirmed | Reviewed change to concurrency, retry behavior, or admission; exact target and service-owner authorization required. | Preserve queued jobs, ordering/idempotency guarantees, and original settings; verify the downstream contract first. | Procedure, owner, and approval unknown; NOT RUN |
|
|
134
|
+
| A rollout-related worker failure is confirmed | Reviewed version-recovery plan tied to an actual deployment record. | Check data and message compatibility; a previous image is not automatically safe to restore. | Procedure and rollback compatibility unknown; NOT RUN |
|
|
135
|
+
| Queue drain or replay is proposed | Queue-provider procedure and data-owner decision, with loss/duplication analysis. | Message deletion or replay can change business outcomes; no such operation is included here. | NOT RUN |
|
|
136
|
+
|
|
137
|
+
No executable mutation or recovery command is supplied because the necessary target evidence and recovery contract are absent.
|
|
138
|
+
|
|
139
|
+
## Escalation and validation
|
|
140
|
+
|
|
141
|
+
Escalation role: worker service owner; if downstream throttling is supported, include the downstream service owner through the verified incident process. Names, contact route, incident link, and next checkpoint are **unknown**. Provide target identity, timestamps, queue definitions, bounded redacted evidence, and the explicit statement that no mutation was performed.
|
|
142
|
+
|
|
143
|
+
| Completion or recovery claim | Required evidence | Actual evidence / state |
|
|
144
|
+
|---|---|---|
|
|
145
|
+
| Correct target and permissions established | Independent inventory comparison and authorized access record | unknown; NOT RUN |
|
|
146
|
+
| Backlog stabilizing or shrinking | Comparable queue metrics over an agreed observation window | unknown; NOT RUN |
|
|
147
|
+
| Job timeliness restored | Oldest age and customer-impact evidence against a verified objective | objective unknown; NOT RUN |
|
|
148
|
+
| No adverse effects from recovery | Verified duplicate/loss/error checks appropriate to the real contract | recovery not performed; NOT RUN |
|
|
149
|
+
|
|
150
|
+
Execution record: run ID `{{run_id}}`; operator **unknown**; observation time **unknown**; actual outcome **NOT RUN**. Follow-up: establish the real service contract, owner, and operational baseline before adapting this example.
|
|
151
|
+
|
|
152
|
+
## Command reference sources
|
|
153
|
+
|
|
154
|
+
These references establish command syntax, not the truth of the simulated observations or compatibility with a particular cluster:
|
|
155
|
+
|
|
156
|
+
- [kubectl get](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_get/)
|
|
157
|
+
- [kubectl logs](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_logs/)
|
|
158
|
+
- [kubectl config view](https://kubernetes.io/docs/reference/kubectl/generated/kubectl_config/kubectl_config_view/)
|
|
@@ -0,0 +1,99 @@
|
|
|
1
|
+
# SYNTHETIC ADR: bounded retries for job submission
|
|
2
|
+
|
|
3
|
+
**SYNTHETIC EXAMPLE — NOT EXECUTED.** This is an invented engineering scenario, not a decision about an existing product. Names, requirements, limits, and proposed behavior below are illustrative. No implementation, approval, security review, or test result is asserted.
|
|
4
|
+
|
|
5
|
+
| Metadata | Value |
|
|
6
|
+
|---|---|
|
|
7
|
+
| Decision lifecycle | proposed |
|
|
8
|
+
| Decision owner | unknown — a service owner has not been assigned |
|
|
9
|
+
| Decision authority / delegated scope | unknown |
|
|
10
|
+
| Reviewer | unknown; security and API contract reviews pending |
|
|
11
|
+
| Revision / date | synthetic revision 0.1 / unknown |
|
|
12
|
+
| Source | Invented scenario premises SYN-01 through SYN-04 below |
|
|
13
|
+
| Jira / related documentation | unknown / unknown |
|
|
14
|
+
| Supersedes | none in this synthetic example |
|
|
15
|
+
| Superseded by | none in this synthetic example |
|
|
16
|
+
| Review trigger | Contract review, security review, changed retry window, or evidence of duplicate job creation |
|
|
17
|
+
| Verification | NOT RUN |
|
|
18
|
+
|
|
19
|
+
The lifecycle is a decision state, not a Confluence publication or deployment state.
|
|
20
|
+
|
|
21
|
+
## Question and scenario premises
|
|
22
|
+
|
|
23
|
+
Should a hypothetical client automatically retry a job-submission request when it cannot tell whether the server accepted the request?
|
|
24
|
+
|
|
25
|
+
| ID | Synthetic premise | Why it matters | Real-world evidence |
|
|
26
|
+
|---|---|---|---|
|
|
27
|
+
| SYN-01 | The example service creates asynchronous work through a proposed `POST /v1/jobs` operation. | A lost response can leave job creation ambiguous to the caller. | unknown; no real API contract supplied |
|
|
28
|
+
| SYN-02 | Duplicate jobs can lead to duplicate notifications and operator work. | Blind retries have a material cost in this scenario. | unknown; no incident or business-rule source supplied |
|
|
29
|
+
| SYN-03 | A candidate client policy has at most three total submission attempts within a 15-minute overall retry budget. | Deduplication retention must cover the allowed retry window and operational delays. | proposed scenario constraint, not an approved service limit |
|
|
30
|
+
| SYN-04 | The proposed design could place a job record, idempotency record, and outbox event in one transactional database. | That atomic boundary could prevent two accepted job records for one key while allowing recoverable queue delivery. | unknown; no database capability or implementation verified |
|
|
31
|
+
|
|
32
|
+
The external worker's effect contract is **unknown**. This decision cannot establish exactly-once execution or downstream side effects without that contract.
|
|
33
|
+
|
|
34
|
+
## Criteria and viable alternatives
|
|
35
|
+
|
|
36
|
+
The priorities below are proposed for this example. No authorized stakeholder has accepted them.
|
|
37
|
+
|
|
38
|
+
| Criterion | A: no automatic retry after ambiguous completion | B: durable idempotency key with bounded retries | C: client-assigned job ID with idempotent `PUT` |
|
|
39
|
+
|---|---|---|---|
|
|
40
|
+
| Avoid duplicate accepted jobs | Avoids retry-induced duplicates, but callers still need reconciliation for an uncertain result. | Proposed key uniqueness and atomic persistence suppress duplicate acceptance within the retention window. | A stable resource ID can express deduplication directly if the contract and authorization rules support it. |
|
|
41
|
+
| Recover from transient response loss | Requires a documented lookup or operator workflow; caller progress may be slow. | Repeating the same key can return the original job identity after a lost response. | Repeating the same resource creation can recover the identity; conflict semantics must be designed. |
|
|
42
|
+
| Implementation and support cost | Lowest write-path change; shifts ambiguity and support work to consumers. | Adds persistent state, concurrency handling, retention, and recovery obligations. | Changes resource naming, ownership, and API semantics; existing clients may need a larger migration. |
|
|
43
|
+
| Contract compatibility | Could preserve the current interface if one existed. | Potentially additive, but actual compatibility remains unknown until the real contract is reviewed. | Likely a larger interface change; its actual impact requires a contract diff. |
|
|
44
|
+
| Security and abuse exposure | No new key store, but existing authorization still applies. | Needs tenant/principal scoping, payload comparison, data minimization, and bounded resource use. | Needs equivalent scope and anti-enumeration controls for caller-selected identifiers. |
|
|
45
|
+
|
|
46
|
+
## Proposed decision
|
|
47
|
+
|
|
48
|
+
Select **B for further design and verification**, because it can make ambiguous submission recoverable while keeping a server-assigned job identity. A is reasonable when ambiguity is rare and a reliable reconciliation workflow exists. C is reasonable for a new API that can expose a caller-selected resource identity. This is a qualitative comparison, not a benchmark.
|
|
49
|
+
|
|
50
|
+
### Candidate contract — illustrative and unverified
|
|
51
|
+
|
|
52
|
+
1. A logical submission has one client-generated `Idempotency-Key`. Retries reuse the same key and the same validated payload. A client must not generate a new key simply because the response was lost.
|
|
53
|
+
2. The proposed uniqueness scope is authenticated tenant, authenticated principal, operation version, and key. Principal changes during a retry are outside this proposed contract and require reconciliation.
|
|
54
|
+
3. The service atomically records the key, a fingerprint of the validated request, one job ID, and an outbox event. Database support for this transaction is a prerequisite, not an established fact.
|
|
55
|
+
4. First acceptance returns proposed status `202` and the job ID. A repeat with the same fingerprint returns that job ID and acceptance status. Reuse with a different fingerprint returns proposed status `409` and does not create a second job.
|
|
56
|
+
5. A concurrent request for the same key must resolve through the same uniqueness constraint. The precise behavior while the first transaction is unresolved remains a contract-review item; it must not create an independent job.
|
|
57
|
+
6. Proposed key retention is 24 hours from acceptance. This is an illustrative design value requiring capacity and policy review. Automatic retries stop after the 15-minute budget; retries after expiry have no deduplication guarantee and require reconciliation rather than a fresh submission.
|
|
58
|
+
7. The proposed client retries transport failures or responses explicitly classified as transient by the final contract, up to three total attempts. Candidate statuses are `408`, `429`, `502`, `503`, and `504`; this list is not yet a deployed guarantee. Use bounded backoff with jitter and honor a valid `Retry-After` only within the remaining retry budget. The backoff parameters and per-attempt timeout remain unknown.
|
|
59
|
+
8. Do not automatically retry validation, authorization, or key/payload conflicts. Report the unresolved outcome when the retry budget expires. The job lookup and reconciliation interface must be specified before implementation.
|
|
60
|
+
|
|
61
|
+
An outbox can publish more than once after recovery. **This proposal deduplicates job acceptance only.** Worker execution and external effects need their own stable job identity, duplicate handling, and verified downstream contract. Acknowledging a queued job is not evidence that its effects completed.
|
|
62
|
+
|
|
63
|
+
## Authority and acceptance conditions
|
|
64
|
+
|
|
65
|
+
| Required evidence | State | Consequence |
|
|
66
|
+
|---|---|---|
|
|
67
|
+
| Named decision authority and delegated scope | unknown | Decision remains proposed. |
|
|
68
|
+
| Explicit choice and approved scope | unknown | This document provides no implementation or deployment approval. |
|
|
69
|
+
| Security review of key scope, retention, abuse controls, and information disclosure | pending | Production acceptance is not established. |
|
|
70
|
+
| Explicit authority for acceptance while security review remains pending | unknown | Do not relabel the ADR accepted with conditions. |
|
|
71
|
+
| API contract and downstream effect review | pending | Status codes, example path, fields, and retry semantics remain illustrative. |
|
|
72
|
+
|
|
73
|
+
If an actual authorized decision later permits conditional acceptance, record the evidence, permitted work, remaining deployment restrictions, condition owner, and exit criteria. Do not infer that exception from this example.
|
|
74
|
+
|
|
75
|
+
## Consequences and obligations
|
|
76
|
+
|
|
77
|
+
| Consequence | Implication / mitigation | Owner / Jira |
|
|
78
|
+
|---|---|---|
|
|
79
|
+
| Persistent deduplication state | Capacity, retention, cleanup, and availability affect submission behavior. Do not expire records before the guaranteed window. | unknown / unknown |
|
|
80
|
+
| Fingerprint stability | Define normalization and versioning from the authoritative schema; avoid storing unnecessary payload data. | unknown / unknown |
|
|
81
|
+
| Outbox delivery may repeat | Consumers must tolerate repeated job IDs; downstream side-effect behavior is still a blocker. | unknown / unknown |
|
|
82
|
+
| Cross-principal retries are outside scope | Document reconciliation and credential-rotation behavior before client adoption. | unknown / unknown |
|
|
83
|
+
| Retention limits the guarantee | Communicate the retry window explicitly; the client must retain its key and known job ID. | unknown / unknown |
|
|
84
|
+
| Rollback may strand accepted jobs or keys | Design compatibility for existing records and queued work before any rollout. | unknown / unknown |
|
|
85
|
+
|
|
86
|
+
## Verification plan
|
|
87
|
+
|
|
88
|
+
| Claim | Verification method | Required observation | Evidence |
|
|
89
|
+
|---|---|---|---|
|
|
90
|
+
| Same key and payload produce one accepted job | Concurrent requests and lost-response simulation against the actual contract | One job record; responses reconcile to the same ID | NOT RUN |
|
|
91
|
+
| Different payload under one key is rejected | Submit two validated but different payloads with one key | Documented conflict; no second job | NOT RUN |
|
|
92
|
+
| Crash recovery does not lose accepted work | Fault injection around transaction commit and outbox publication | Accepted job remains discoverable; outbox resumes without creating a new job | NOT RUN |
|
|
93
|
+
| Tenant/principal boundary is enforced | Authorization review and cross-scope contract tests | No unintended data disclosure or collision across authorized scopes | NOT RUN |
|
|
94
|
+
| Retry policy respects all budgets | Simulated transient failures, long `Retry-After`, and timeouts | At most three attempts, no retry outside overall budget, explicit unresolved outcome | NOT RUN |
|
|
95
|
+
| Worker effects tolerate duplicate delivery | Review and test against the material downstream schema | Defined duplicate outcome without an unsupported exactly-once claim | BLOCKED — schema unknown; NOT RUN |
|
|
96
|
+
|
|
97
|
+
## Reconsideration
|
|
98
|
+
|
|
99
|
+
Revisit the proposal if the actual API already has a stable operation ID, the database cannot provide the required atomic boundary, retry windows change, the downstream contract invalidates duplicate handling, or measured support cost favors another alternative. Supersession must link a new authorized decision; no such decision exists here.
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg">
|
|
2
|
+
<path d="M19.58 4.38996C18.05 2.86996 15.68 2.88996 14.18 4.38996L5.26999 13.33C4.25999 14.34 3.84999 14.92 3.59999 16.26L3.06999 19.56C2.88999 20.47 3.50999 21.09 4.43999 20.93L7.74999 20.39C9.06999 20.18 9.64999 19.76 10.66 18.75L19.58 9.82996C21.1 8.30996 21.12 5.93996 19.58 4.40996V4.38996Z" fill="#FEBD08"/>
|
|
3
|
+
<path d="M19.58 9.81997C21.1 8.29997 21.12 5.92997 19.58 4.39997C18.05 2.87997 15.68 2.89997 14.18 4.39997L13.77 4.80997L19.18 10.22L19.58 9.81997Z" fill="#FF928C"/>
|
|
4
|
+
<path d="M13.7694 4.81308L12.3552 6.22729L17.7646 11.6367L19.1788 10.2224L13.7694 4.81308Z" fill="#D9D9D9"/>
|
|
5
|
+
<path opacity="0.5" d="M12.36 6.22998L5.26998 13.34C4.25998 14.35 3.84998 14.93 3.59998 16.27L3.06998 19.57C2.97998 20.02 3.08998 20.4 3.32998 20.65L15.05 8.92998L12.36 6.22998Z" fill="white"/>
|
|
6
|
+
<path d="M4.60001 14.05C4.06001 14.69 3.79001 15.27 3.60001 16.26L3.51001 16.81L7.18001 20.48L7.75001 20.39C8.74001 20.23 9.31001 19.96 9.95001 19.41L4.60001 14.05Z" fill="#FFDDBC"/>
|
|
7
|
+
<path d="M3.50999 16.8101L3.06999 19.5601C2.88999 20.4701 3.50999 21.0901 4.43999 20.9301L7.17999 20.4801L3.50999 16.8101Z" fill="#4D4D4D"/>
|
|
8
|
+
</svg>
|