fix(docs): correcting documentation for knowledge policy

Author: orneryd

docs/features/memory-decay.md

@@ -181,14 +181,23 @@ Nodes and edges whose decay score drops below the visibility threshold are autom
 
 A background job periodically removes suppressed entities from secondary indexes (BM25, vector) to reclaim space. Primary data remains intact.
 
-## Admin Endpoints
+## Cypher Introspection
 
-| Endpoint | Description |
-|----------|-------------|
-| `GET /admin/knowledge-policies/profiles` | List decay profiles and bindings |
-| `GET /admin/knowledge-policies/policies` | List promotion policies |
-| `GET /admin/knowledge-policies/resolve?entityId=X` | Explain scoring for an entity |
-| `GET /admin/knowledge-policies/deindex/status` | Deindex cleanup job status |
+The supported operational surface for knowledge-layer scoring is Cypher, not a dedicated admin HTTP API.
+
+```cypher
+CALL nornicdb.knowledgepolicy.info();
+CALL nornicdb.knowledgepolicy.profiles();
+CALL nornicdb.knowledgepolicy.policies();
+CALL nornicdb.knowledgepolicy.resolve('nornic:episode-1', '', '');
+CALL nornicdb.knowledgepolicy.deindexStatus();
+
+SHOW DECAY PROFILES;
+SHOW PROMOTION PROFILES;
+SHOW PROMOTION POLICIES;
+```
+
+Use these procedures to inspect effective policy resolution, catalog stored profiles and policies, and monitor deindex cleanup state.
 
 ## Disable Scoring
 

docs/user-guides/knowledge-layer-policies.md

@@ -108,14 +108,42 @@ When multiple bindings could match:
 3. If two bindings have equal specificity, the resolver returns a diagnostic warning
 4. No binding → entity scores 1.0 (no decay)
 
-## Admin API
+## Cypher Diagnostics
 
-| Endpoint | Description |
-|----------|-------------|
-| `GET /admin/knowledge-policies/profiles` | List all profiles and bindings |
-| `GET /admin/knowledge-policies/policies` | List all promotion policies |
-| `GET /admin/knowledge-policies/resolve?entityId=X` | Explain scoring for a specific entity |
-| `GET /admin/knowledge-policies/deindex/status` | Deindex cleanup job status |
+The knowledge-layer system is operated and inspected through Cypher.
+
+### Catalog and Status
+
+```cypher
+CALL nornicdb.knowledgepolicy.info();
+CALL nornicdb.knowledgepolicy.profiles();
+CALL nornicdb.knowledgepolicy.policies();
+
+SHOW DECAY PROFILES;
+SHOW PROMOTION PROFILES;
+SHOW PROMOTION POLICIES;
+```
+
+### Resolve an Effective Policy
+
+```cypher
+-- Resolve by entity ID
+CALL nornicdb.knowledgepolicy.resolve('nornic:episode-1', '', '');
+
+-- Resolve by label set
+CALL nornicdb.knowledgepolicy.resolve('', 'MemoryEpisode,SessionRecord', '');
+
+-- Resolve by edge type
+CALL nornicdb.knowledgepolicy.resolve('', '', 'CO_ACCESSED');
+```
+
+### Deindex Queue Status
+
+```cypher
+CALL nornicdb.knowledgepolicy.deindexStatus();
+```
+
+These procedures are the supported diagnostics surface. The older `/admin/knowledge-policies/*` HTTP endpoints have been removed.
 
 ## Browser UI
 
@@ -124,6 +152,8 @@ The Knowledge Policies admin page is available at **Security > Knowledge Policie
 - Interactive resolve tool for debugging scoring
 - Deindex status monitoring
 
+The UI uses the same Cypher DDL and knowledge-policy procedures shown above rather than a separate admin API.
+
 Node detail views in the graph browser show decay metadata (score, suppression status, access count) when present.
 
 ## See Also

docs/user-guides/visibility-suppression-deindex.md

@@ -65,14 +65,13 @@ ORDER BY decayScore(n)
 
 `reveal()` is a query-time bypass — it does not change the entity's suppression status. The entity remains suppressed for all other queries.
 
-### Using the Admin API
+### Inspecting Suppression with Cypher
 
-```bash
-curl -H "Authorization: Bearer $TOKEN" \
-  "http://localhost:7474/admin/knowledge-policies/resolve?entityId=node-123"
+```cypher
+CALL nornicdb.knowledgepolicy.resolve('node-123', '', '');
 ```
 
-Returns the full `ScoringResolution` including explanation of why the entity was suppressed.
+This returns the full scoring resolution, including the effective threshold, final score, suppression eligibility, and explanation of why the entity was suppressed.
 
 ## Deindex Cleanup
 
@@ -91,28 +90,16 @@ The deindex job runs every 24 hours by default. No configuration is required —
 
 ### Monitoring
 
-Check deindex status via the admin API:
+Check deindex status with the supported Cypher procedure:
 
-```bash
-curl -H "Authorization: Bearer $TOKEN" \
-  "http://localhost:7474/admin/knowledge-policies/deindex/status"
+```cypher
+CALL nornicdb.knowledgepolicy.deindexStatus();
 ```
 
-Response:
-```json
-{
-  "pending_count": 3,
-  "items": [
-    {
-      "workItemId": "deindex:nornic:node-123",
-      "targetId": "node-123",
-      "targetScope": "NODE",
-      "enqueuedAt": 1714000000,
-      "status": "pending"
-    }
-  ],
-  "supported": true
-}
+Example result columns:
+
+```text
+pending_count | supported | message | workItemId | targetId | targetScope | enqueuedAt | status
 ```
 
 The browser UI also shows deindex status on the **Security > Knowledge Policies > Deindex Status** tab.