Files
llm-connect/.custodian-brief.md
tegwick 1edc02de7c
Some checks failed
CI / test (3.10) (push) Has been cancelled
CI / test (3.11) (push) Has been cancelled
CI / test (3.12) (push) Has been cancelled
chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-06-07:
  - update .custodian-brief.md for llm-connect
2026-06-07 11:46:51 +02:00

29 lines
1.2 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — llm-connect
**Domain:** custodian
**Last synced:** 2026-06-07 09:46 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Activity-Core Always-On LLM Endpoint
Progress: 0/7 done | workstream_id: `8de71d58-1193-424f-8338-a9aa4e173c5b`
**Open tasks:**
- · Lock activity-core daily WSJF request and schema fixture `f1d21c4b`
- · Resolve custodian-triage-balanced to provider, model, and RunConfig defaults `4538bae3`
- · Return useful non-secret provider and transport errors from server mode `d4adfe3b`
- · Add container packaging and service entrypoint for llm-connect server `38822b17`
- · Provide Kubernetes Deployment, Service, probes, and secret references `f9743610`
- · Validate health, fixture execute, JSON schema content, and timeout budget `f046d68b`
- · Publish verified LLM_CONNECT_URL handoff and activity-core smoke evidence `92e043f0`
---
## MCP Orientation (when available)
If the state-hub MCP server is reachable, call:
`get_domain_summary("custodian")`
This provides richer cross-domain context.
If the MCP call fails, use this file as your orientation source.