@geraldmaron/construct 1.4.2 → 1.5.0

package/specialists/org/contracts/architect-to-evaluator.json

@@ -1,7 +1,7 @@
 {
   "id": "architect-to-evaluator",
   "producer": "cx-architect",
-  "consumer": "cx-evaluator",
+  "consumer": "cx-reviewer",
   "trigger": {
     "riskFlags": [
       "ai",
@@ -34,19 +34,29 @@
     "Baseline run identified or scheduled before proposed change runs"
   ],
   "postconditions": [
-    "Failing case is defined before results are seen",
-    "Regression checks enumerated; not just success-path test cases",
+    {
+      "id": "architect-to-evaluator-pc-0-failing-case-is-defined-before-results",
+      "description": "Failing case is defined before results are seen",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "architect-to-evaluator-pc-1-regression-checks-enumerated-not-just-success",
+      "description": "Regression checks enumerated; not just success-path test cases",
+      "postconditionType": "advisory"
+    },
     {
       "id": "eval-spec-has-success-criteria",
       "description": "Eval spec must contain a Success Criteria section",
       "check": "artifact-has-section",
-      "section": "Success Criteria"
+      "section": "Success Criteria",
+      "postconditionType": "executable"
     },
     {
       "id": "eval-spec-has-baseline",
       "description": "Eval spec must contain a Baseline section",
       "check": "artifact-has-section",
-      "section": "Baseline"
+      "section": "Baseline",
+      "postconditionType": "executable"
     }
   ],
   "description": "",

package/specialists/org/contracts/architect-to-legal-compliance.json

@@ -1,7 +1,7 @@
 {
   "id": "architect-to-legal-compliance",
   "producer": "cx-architect",
-  "consumer": "cx-legal-compliance",
+  "consumer": "cx-security",
   "trigger": {
     "riskFlags": [
       "compliance",
@@ -30,19 +30,29 @@
     "Dependency tree surfaced past the first layer for licensing review"
   ],
   "postconditions": [
-    "Every assertion cites the regulation, standard, or contract clause it rests on",
-    "AI-generated user-facing content has a disclosure strategy noted, or is marked not-applicable with reason",
+    {
+      "id": "architect-to-legal-compliance-pc-0-every-assertion-cites-the-regulation-standard",
+      "description": "Every assertion cites the regulation, standard, or contract clause it rests on",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "architect-to-legal-compliance-pc-1-ai-generated-user-facing-content-has",
+      "description": "AI-generated user-facing content has a disclosure strategy noted, or is marked not-applicable with reason",
+      "postconditionType": "advisory"
+    },
     {
       "id": "compliance-memo-has-regulatory-citations",
       "description": "Compliance memo must contain a Regulatory Citations section",
       "check": "artifact-has-section",
-      "section": "Regulatory Citations"
+      "section": "Regulatory Citations",
+      "postconditionType": "executable"
     },
     {
       "id": "compliance-memo-has-remediation-plan",
       "description": "Compliance memo must contain a Remediation Plan section",
       "check": "artifact-has-section",
-      "section": "Remediation Plan"
+      "section": "Remediation Plan",
+      "postconditionType": "executable"
     }
   ],
   "description": "",

package/specialists/org/contracts/architect-to-operations.json

@@ -23,7 +23,8 @@
       "sequencedTasks",
       "dependencyGraph",
       "ownershipMatrix",
-      "verificationGates"
+      "verificationGates",
+      "slippageRisk"
     ]
   },
   "preconditions": [
@@ -31,9 +32,21 @@
     "Tasks are atomic and individually verifiable"
   ],
   "postconditions": [
-    "Every task names a single owner",
-    "Every task names a verification gate and definition-of-done",
-    "Dependency graph identifies blockers; no task lies on a hidden critical path"
+    {
+      "id": "architect-to-operations-pc-0-every-task-names-a-single-owner",
+      "description": "Every task names a single owner",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "architect-to-operations-pc-1-every-task-names-a-verification-gate",
+      "description": "Every task names a verification gate and definition-of-done",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "architect-to-operations-pc-2-dependency-graph-identifies-blockers-no-task",
+      "description": "Dependency graph identifies blockers; no task lies on a hidden critical path",
+      "postconditionType": "advisory"
+    }
   ],
   "description": "",
   "teamBoundary": {

package/specialists/org/contracts/architect-to-platform-engineer.json

@@ -1,7 +1,7 @@
 {
   "id": "architect-to-platform-engineer",
   "producer": "cx-architect",
-  "consumer": "cx-platform-engineer",
+  "consumer": "cx-engineer",
   "trigger": {
     "riskFlags": [
       "platform",
@@ -34,9 +34,25 @@
     "Existing CI/CD and tooling surveyed before proposing new tooling"
   ],
   "postconditions": [
-    "Migration path described for existing workflows",
-    "Rollback procedure exists in case the change makes things worse",
-    "Improvement removes more configuration than it adds, or the added config is justified"
+    {
+      "id": "architect-to-platform-engineer-pc-0-migration-path-described-for-existing-workflows",
+      "description": "Migration path described for existing workflows",
+      "postconditionType": "executable",
+      "enforcedVia": "output-shape",
+      "enforcedBy": "migration"
+    },
+    {
+      "id": "architect-to-platform-engineer-pc-1-rollback-procedure-exists-in-case-the",
+      "description": "Rollback procedure exists in case the change makes things worse",
+      "postconditionType": "executable",
+      "enforcedVia": "output-shape",
+      "enforcedBy": "rollback"
+    },
+    {
+      "id": "architect-to-platform-engineer-pc-2-improvement-removes-more-configuration-than-it",
+      "description": "Improvement removes more configuration than it adds, or the added config is justified",
+      "postconditionType": "advisory"
+    }
   ],
   "description": ""
 }

package/specialists/org/contracts/construct-to-orchestrator.json

@@ -25,8 +25,16 @@
     "docAuthoring.owner present if authoring a typed document"
   ],
   "postconditions": [
-    "Dispatch plan emitted with specialists in sequence",
-    "Parallel work marked with [parallel: ...] tags"
+    {
+      "id": "construct-to-orchestrator-pc-0-dispatch-plan-emitted-with-specialists-in",
+      "description": "Dispatch plan emitted with specialists in sequence",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "construct-to-orchestrator-pc-1-parallel-work-marked-with-parallel-tags",
+      "description": "Parallel work marked with [parallel: ...] tags",
+      "postconditionType": "advisory"
+    }
   ],
   "skillHints": [
     "ai/orchestration-workflow",

package/specialists/org/contracts/data-analyst-to-product-manager.json

@@ -30,8 +30,17 @@
     "Metric definition reviewed for vanity-metric risk and for hit-without-solving-the-problem risk"
   ],
   "postconditions": [
-    "PRD success metrics carry the cited baseline and threshold from the analysis",
-    "Metrics that can be hit without solving the problem are flagged and replaced"
+    {
+      "id": "data-analyst-to-product-manager-pc-0-prd-success-metrics-carry-the-cited",
+      "description": "PRD success metrics carry the cited baseline and threshold from the analysis",
+      "postconditionType": "executable",
+      "check": "artifact-claims-cited"
+    },
+    {
+      "id": "data-analyst-to-product-manager-pc-1-metrics-that-can-be-hit-without",
+      "description": "Metrics that can be hit without solving the problem are flagged and replaced",
+      "postconditionType": "advisory"
+    }
   ],
   "description": "",
   "teamBoundary": {

package/specialists/org/contracts/engineer-to-qa.json

@@ -9,7 +9,9 @@
     "schema": "lib/contract-schemas/implementation.json",
     "mustContain": [
       "filesChanged",
-      "tests"
+      "tests",
+      "effortClass",
+      "blastRadius"
     ]
   },
   "output": {
@@ -20,9 +22,23 @@
     "Test plan exists or is derivable from acceptance criteria"
   ],
   "postconditions": [
-    "Verdict in {PASS, FAIL}",
-    "Coverage meets project threshold",
-    "FAIL blocks DONE in workflow"
+    {
+      "id": "engineer-to-qa-pc-0-verdict-in-pass-fail",
+      "description": "Verdict in {PASS, FAIL}",
+      "postconditionType": "executable",
+      "enforcedVia": "output-shape",
+      "enforcedBy": "verdict (schema enum)"
+    },
+    {
+      "id": "engineer-to-qa-pc-1-coverage-meets-project-threshold",
+      "description": "Coverage meets project threshold",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "engineer-to-qa-pc-2-fail-blocks-done-in-workflow",
+      "description": "FAIL blocks DONE in workflow",
+      "postconditionType": "advisory"
+    }
   ],
   "description": "",
   "teamBoundary": {

package/specialists/org/contracts/engineer-to-reviewer.json

@@ -9,7 +9,11 @@
     "schema": "lib/contract-schemas/implementation.json",
     "mustContain": [
       "filesChanged",
-      "verificationChecklist"
+      "verificationChecklist",
+      "feasibilityAssessment",
+      "effortClass",
+      "debtNote",
+      "blastRadius"
     ]
   },
   "output": {
@@ -37,10 +41,30 @@
     "Tests compiled; static analysis run"
   ],
   "postconditions": [
-    "Verdict in {APPROVED, APPROVED_WITH_WARNINGS, BLOCKED}",
-    "BLOCKED verdict stops downstream work until addressed",
-    "CRITICAL findings prevent release",
-    "Either findings is non-empty or noIssuesFoundAt enumerates the inspected paths — prevents silent rubber-stamp reviews"
+    {
+      "id": "engineer-to-reviewer-pc-0-verdict-in-approved-approved-with-warnings",
+      "description": "Verdict in {APPROVED, APPROVED_WITH_WARNINGS, BLOCKED}",
+      "postconditionType": "executable",
+      "enforcedVia": "output-shape",
+      "enforcedBy": "verdict (mustMatchEnum)"
+    },
+    {
+      "id": "engineer-to-reviewer-pc-1-blocked-verdict-stops-downstream-work-until",
+      "description": "BLOCKED verdict stops downstream work until addressed",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "engineer-to-reviewer-pc-2-critical-findings-prevent-release",
+      "description": "CRITICAL findings prevent release",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "engineer-to-reviewer-pc-3-either-findings-is-non-empty-or",
+      "description": "Either findings is non-empty or noIssuesFoundAt enumerates the inspected paths — prevents silent rubber-stamp reviews",
+      "postconditionType": "executable",
+      "enforcedVia": "output-shape",
+      "enforcedBy": "findings|noIssuesFoundAt (mustContainOneOf)"
+    }
   ],
   "description": "",
   "teamBoundary": {

package/specialists/org/contracts/explorer-to-engineer.json

@@ -1,6 +1,6 @@
 {
   "id": "explorer-to-engineer",
-  "producer": "cx-explorer",
+  "producer": "cx-researcher",
   "consumer": "cx-engineer",
   "trigger": {
     "intent": [
@@ -25,8 +25,16 @@
     "Exploration findings reviewed; gaps and surprising dependencies surfaced"
   ],
   "postconditions": [
-    "Implementation reads the files cited in keyFiles before edits",
-    "Gaps named by explorer (missing tests, missing error handling) are addressed or filed"
+    {
+      "id": "explorer-to-engineer-pc-0-implementation-reads-the-files-cited-in",
+      "description": "Implementation reads the files cited in keyFiles before edits",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "explorer-to-engineer-pc-1-gaps-named-by-explorer-missing-tests",
+      "description": "Gaps named by explorer (missing tests, missing error handling) are addressed or filed",
+      "postconditionType": "advisory"
+    }
   ],
   "description": "",
   "teamBoundary": {

package/specialists/org/contracts/legal-compliance-to-release-manager.json

@@ -1,7 +1,7 @@
 {
   "id": "legal-compliance-to-release-manager",
-  "producer": "cx-legal-compliance",
-  "consumer": "cx-release-manager",
+  "producer": "cx-security",
+  "consumer": "cx-operations",
   "trigger": {
     "riskFlags": [
       "compliance"
@@ -30,8 +30,16 @@
     "All must-fix compliance items closed or accepted in writing by the release owner"
   ],
   "postconditions": [
-    "Release blocks if any must-fix item is unresolved",
-    "Should-fix items carry a tracking issue and an owner"
+    {
+      "id": "legal-compliance-to-release-manager-pc-0-release-blocks-if-any-must-fix",
+      "description": "Release blocks if any must-fix item is unresolved",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "legal-compliance-to-release-manager-pc-1-should-fix-items-carry-a-tracking",
+      "description": "Should-fix items carry a tracking issue and an owner",
+      "postconditionType": "advisory"
+    }
   ],
   "description": "",
   "teamBoundary": {

package/specialists/org/contracts/operations-to-user.json

@@ -0,0 +1,53 @@
+{
+  "id": "operations-tpm-briefing",
+  "producer": "cx-operations",
+  "consumer": "user",
+  "trigger": {
+    "intent": ["implementation"],
+    "workCategory": "deep"
+  },
+  "input": {
+    "shape": "bound-snapshot-slice",
+    "mustContain": [
+      "snapshotSections"
+    ]
+  },
+  "output": {
+    "shape": "tpm-briefing",
+    "mustContain": [
+      "coverageMatrix",
+      "missingWork",
+      "timelineRisks",
+      "misalignment",
+      "proposals",
+      "provenance"
+    ]
+  },
+  "preconditions": [
+    "The operations specialist's bound provider snapshot has been sliced (Jira + Confluence + Slack sections present or explicitly empty)",
+    "Provider bindings and filters have been enforced at read time before the slice reaches analysis"
+  ],
+  "postconditions": [
+    {
+      "id": "operations-tpm-briefing-pc-0-every-missing-work-finding-cites-the",
+      "description": "Every missing-work finding cites the requirement id and the empty coverage",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "operations-tpm-briefing-pc-1-every-timeline-risk-finding-cites-its",
+      "description": "Every timeline-risk finding cites its evidence (issue id, due date, blocking chain)",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "operations-tpm-briefing-pc-2-every-proposal-names-the-provider-write",
+      "description": "Every proposal names the provider write kind and traces to an uncovered requirement",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "operations-tpm-briefing-pc-3-no-load-bearing-claim-is-present",
+      "description": "No load-bearing claim is present without a source id; unknowns are marked, never invented",
+      "postconditionType": "advisory"
+    }
+  ],
+  "description": "Recurring TPM briefing produced by the operations specialist over its bound Jira + Confluence + Slack snapshot: PRD-versus-epic coverage, timeline risk, misalignment, and approval-gated ticket proposals."
+}

package/specialists/org/contracts/operations-triage-output.json

@@ -0,0 +1,53 @@
+{
+  "id": "operations-triage",
+  "producer": "cx-operations",
+  "consumer": "user",
+  "trigger": {
+    "intent": ["implementation"],
+    "workCategory": "deep"
+  },
+  "input": {
+    "shape": "bound-snapshot-slice",
+    "mustContain": [
+      "snapshotSections"
+    ]
+  },
+  "output": {
+    "shape": "triage-briefing",
+    "mustContain": [
+      "inventoried",
+      "duplicates",
+      "underspecified",
+      "proposals",
+      "provenance",
+      "summary"
+    ]
+  },
+  "preconditions": [
+    "The operations specialist's bound provider snapshot has been sliced (Jira + Confluence sections present or explicitly empty)",
+    "Provider bindings and filters have been enforced at read time before the slice reaches triage"
+  ],
+  "postconditions": [
+    {
+      "id": "operations-triage-pc-0-every-duplicate-finding-cites-the-issue",
+      "description": "Every duplicate finding cites the issue keys being compared",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "operations-triage-pc-1-every-under-specified-finding-cites-the",
+      "description": "Every under-specified finding cites the issue key and the reasons",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "operations-triage-pc-2-every-proposal-carries-a-typed-writeintent",
+      "description": "Every proposal carries a typed writeIntent (duplicate-link or needs-info comment) and traces to its source issue",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "operations-triage-pc-3-no-provider-write-executes-without-approval",
+      "description": "No provider write executes without approval; no load-bearing claim is present without a source id",
+      "postconditionType": "advisory"
+    }
+  ],
+  "description": "Triage briefing produced by the operations specialist over its bound Jira + Confluence snapshot: inventoried tickets, detected duplicates, under-specified issues, and approval-gated triage proposals."
+}

package/specialists/org/contracts/pm-requirements-candidates.json

@@ -0,0 +1,53 @@
+{
+  "id": "pm-requirements-candidates",
+  "producer": "cx-product-manager",
+  "consumer": "user",
+  "trigger": {
+    "intent": ["implementation"],
+    "workCategory": "deep"
+  },
+  "input": {
+    "shape": "bound-snapshot-slice",
+    "mustContain": [
+      "snapshotSections"
+    ]
+  },
+  "output": {
+    "shape": "requirements-candidates",
+    "mustContain": [
+      "candidates",
+      "clusters",
+      "requirements",
+      "provenance",
+      "summary"
+    ]
+  },
+  "preconditions": [
+    "The product-manager specialist's bound provider snapshot has been sliced (feedback + Confluence sections present or explicitly empty)",
+    "Provider bindings and filters have been enforced at read time before the slice reaches analysis",
+    "Feedback-item text is stamped EXTERNAL_UNAUTHENTICATED (B14/N1) and is treated as quoted evidence, never as instruction"
+  ],
+  "postconditions": [
+    {
+      "id": "pm-requirements-candidates-pc-0-every-requirements-candidate-cites-the",
+      "description": "Every requirements-candidate cites the feedback rows it was clustered from and, when matched, the PRD requirement id it relates to",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "pm-requirements-candidates-pc-1-every-candidates-relation-is-one-of",
+      "description": "Every candidate's relation is one of supports, contradicts, or new — new is used only when no PRD requirement matched",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "pm-requirements-candidates-pc-2-no-load-bearing-claim-is-present",
+      "description": "No load-bearing claim is present without a source id; unknowns are marked, never invented",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "pm-requirements-candidates-pc-3-no-provider-write-executes-this-preset",
+      "description": "No provider write executes: this preset is artifact-only and proposes no writeIntent",
+      "postconditionType": "advisory"
+    }
+  ],
+  "description": "Requirements-candidates artifact produced by the product-manager specialist over its bound feedback + Confluence snapshot: feedback clustered by theme, scored with the user-value rubric, and cross-referenced against PRD requirements."
+}

package/specialists/org/contracts/product-manager-to-architect.json

@@ -17,7 +17,10 @@
       "functionalRequirements",
       "nonFunctionalRequirements",
       "acceptanceCriteria",
-      "constraints"
+      "constraints",
+      "valueStatement",
+      "tradeoffTable",
+      "prioritizationCall"
     ]
   },
   "output": {
@@ -25,40 +28,57 @@
     "type": "decision"
   },
   "preconditions": [
-    "cx-devil-advocate framing challenge logged if riskFlags.architecture"
+    "cx-reviewer framing challenge logged if riskFlags.architecture"
   ],
   "postconditions": [
-    "ADR Problem section traces to PRD Problem, not to tickets",
-    "ADR Rejected alternatives section present with ≥2 alternatives and specific rejection reasons",
-    "Reversibility section states whether one-way or two-way door",
+    {
+      "id": "product-manager-to-architect-pc-0-adr-problem-section-traces-to-prd",
+      "description": "ADR Problem section traces to PRD Problem, not to tickets",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "product-manager-to-architect-pc-1-adr-rejected-alternatives-section-present-with",
+      "description": "ADR Rejected alternatives section present with ≥2 alternatives and specific rejection reasons",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "product-manager-to-architect-pc-2-reversibility-section-states-whether-one-way",
+      "description": "Reversibility section states whether one-way or two-way door",
+      "postconditionType": "advisory"
+    },
     {
       "id": "adr-has-rejected-alternatives",
       "description": "ADR must contain a Rejected Alternatives section",
       "check": "artifact-has-section",
-      "section": "Rejected Alternatives"
+      "section": "Rejected Alternatives",
+      "postconditionType": "executable"
     },
     {
       "id": "adr-reversibility-stated",
       "description": "ADR Reversibility section is present and non-empty",
       "check": "artifact-section-nonempty",
-      "section": "Reversibility"
+      "section": "Reversibility",
+      "postconditionType": "executable"
     },
     {
       "id": "adr-consequences-stated",
       "description": "ADR Consequences section is present and non-empty",
       "check": "artifact-section-nonempty",
-      "section": "Consequences"
+      "section": "Consequences",
+      "postconditionType": "executable"
     },
     {
       "id": "adr-numeric-claims-cited",
       "description": "Every numeric claim in the ADR body cites a source",
-      "check": "artifact-claims-cited"
+      "check": "artifact-claims-cited",
+      "postconditionType": "executable"
     },
     {
       "id": "adr-manifest-reviewers",
       "description": "Manifest required reviewers must appear in agent log before handoff",
       "check": "artifact-reviewers-seen",
-      "fromManifest": true
+      "fromManifest": true,
+      "postconditionType": "executable"
     }
   ],
   "description": "",

package/specialists/org/contracts/product-manager-to-data-analyst.json

@@ -31,12 +31,22 @@
     "Success definition stated in writing before metric design begins"
   ],
   "postconditions": [
-    "Every percentage, multiplier, or magnitude cites the query, dashboard, or run that produced it",
-    "Baseline is a measured value or names the plan to establish one",
+    {
+      "id": "product-manager-to-data-analyst-pc-0-every-percentage-multiplier-or-magnitude-cites",
+      "description": "Every percentage, multiplier, or magnitude cites the query, dashboard, or run that produced it",
+      "postconditionType": "executable",
+      "check": "artifact-claims-cited"
+    },
+    {
+      "id": "product-manager-to-data-analyst-pc-1-baseline-is-a-measured-value-or",
+      "description": "Baseline is a measured value or names the plan to establish one",
+      "postconditionType": "advisory"
+    },
     {
       "id": "metrics-analysis-claims-cited",
       "description": "Every numeric claim in the analysis cites the query or dashboard",
-      "check": "artifact-claims-cited"
+      "check": "artifact-claims-cited",
+      "postconditionType": "executable"
     }
   ],
   "description": "",

package/specialists/org/contracts/product-manager-to-ux-researcher.json

@@ -1,7 +1,7 @@
 {
   "id": "product-manager-to-ux-researcher",
   "producer": "cx-product-manager",
-  "consumer": "cx-ux-researcher",
+  "consumer": "cx-researcher",
   "trigger": {
     "docAuthoring.docType": [
       "prd",
@@ -33,18 +33,28 @@
     "PRD has an open user-research question; PRD not finalized"
   ],
   "postconditions": [
-    "Every friction-map entry cites the observation or session it came from",
-    "Stated preferences are labeled distinctly from observed behaviors",
+    {
+      "id": "product-manager-to-ux-researcher-pc-0-every-friction-map-entry-cites-the",
+      "description": "Every friction-map entry cites the observation or session it came from",
+      "postconditionType": "advisory"
+    },
+    {
+      "id": "product-manager-to-ux-researcher-pc-1-stated-preferences-are-labeled-distinctly-from",
+      "description": "Stated preferences are labeled distinctly from observed behaviors",
+      "postconditionType": "advisory"
+    },
     {
       "id": "ux-research-has-sources-section",
       "description": "UX research artifact must contain a Sources section",
       "check": "artifact-has-section",
-      "section": "Sources"
+      "section": "Sources",
+      "postconditionType": "executable"
     },
     {
       "id": "ux-research-claims-cited",
       "description": "Every numeric or generalization claim in the UX brief cites the research source",
-      "check": "artifact-claims-cited"
+      "check": "artifact-claims-cited",
+      "postconditionType": "executable"
     }
   ],
   "description": ""