Expose functional benefic malefic strict evidence

2026-06-28 16:53:53 +08:00
parent a4ad9d716e
commit 8c404ec64d
4 changed files with 194 additions and 4 deletions
@@ -52,8 +52,9 @@ This file is the small index for the current engineering fronts that still drive
 - `/Users/wuyongnaren/Documents/印度占星/docs/superpowers/specs/2026-06-28-dignity-guardrail-v1-design.md`
 - `/Users/wuyongnaren/Documents/印度占星/docs/research/dignity_guardrail_v1_boundary_audit_2026_06_28.md`
 - `/Users/wuyongnaren/Documents/印度占星/docs/research/divisional_dignity_context_repair_audit_2026_06_28.md`
+- `/Users/wuyongnaren/Documents/印度占星/docs/research/functional_benefic_malefic_strict_layer_audit_2026_06_28.md`
 - D1-only dignity guardrail is landed.
 - Divisional dignity context repair for D9/DK/Vimsopaka Navamsa is also landed.
 - Still open:
  - Vimsopaka semantic mapping for `NEECHA_BHANGA / GREAT_FRIEND / GREAT_ENEMY`
-  - a separate functional-role guardrail
+  - functional role now enters strict evidence; follow-up is Technique Audit Table rendering.
@@ -0,0 +1,42 @@
+# Functional Benefic/Malefic Strict Layer Audit - 2026-06-28
+
+## Scope
+
+This audit records the first strict-workflow integration of the Functional Benefic/Malefic hard constraint from `AGENTS.md`.
+
+## Implementation
+
+Strict workflow evidence now exposes:
+
+```json
+{
+  "functional_benefic_malefic": {
+    "status": "used | blocked",
+    "ascendant": "Leo",
+    "functional_benefics": ["Sun", "Mars", "Jupiter"],
+    "functional_malefics": ["Mercury", "Moon", "Saturn", "Venus"],
+    "functional_neutrals": [],
+    "yogakarakas": ["Mars"],
+    "owned_houses": {"Sun": [1]},
+    "source": "strict_functional_benefic_malefic_v1"
+  }
+}
+```
+
+## Boundary
+
+- This is a functional house-lord role layer, not a natural benefic/malefic table.
+- It is exposed as evidence and secondary context.
+- It does not directly lift dominant labels.
+- If chart ascendant or planets are unavailable, the layer remains `blocked` in evidence but does not pollute legacy secondary-context tests.
+
+## Why It Matters
+
+The project hard constraint says high-rigor timing or outcome readings must not judge benefic/malefic effects from natural planetary quality alone. This bridge makes the functional role layer visible to strict workflows so later adjudicators and Technique Audit Tables can use it.
+
+## Verification
+
+- `tests/test_mcp_strict_workflow_functional_layer.py`
+- `tests/test_mcp_strict_workflow_relationship.py`
+- `tests/test_mcp_strict_workflow_career.py`
+- `tests/test_mcp_strict_workflow_finance.py`