quality gate layer

docs/ARCHITECTURE-BLUEPRINT.md

@@ -243,6 +243,10 @@ Architecture lesson:
 Repository quality packs should be normal extensions. A score is not a
 certification verdict; it is a normalized finding and trend signal.
 
+Quality gates should be core policy decisions over retained posture, not
+extension-specific verdicts. The first gate layer checks latest run status,
+unexpected finding count, and whether the latest trend regressed.
+
 Sources:
 
 - [OpenSSF Scorecard](https://openssf.org/projects/scorecard/)

docs/schemas/gate-summary.schema.json

@@ -0,0 +1,28 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "title": "Guide Board Gate Summary",
+  "type": "object",
+  "additionalProperties": false,
+  "required": [
+    "id",
+    "created_at",
+    "trend_summary_ref",
+    "status",
+    "policy",
+    "group_count",
+    "passed_groups",
+    "failed_groups",
+    "groups"
+  ],
+  "properties": {
+    "id": { "type": "string" },
+    "created_at": { "type": "string" },
+    "trend_summary_ref": { "type": "string" },
+    "status": { "type": "string" },
+    "policy": { "type": "object" },
+    "group_count": { "type": "integer" },
+    "passed_groups": { "type": "integer" },
+    "failed_groups": { "type": "integer" },
+    "groups": { "type": "array", "items": { "type": "object" } }
+  }
+}