lda.chat/lda-wf
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test: prove platform sources need no bindings

Browse Source
This commit is contained in:
lda
2026-06-13 18:56:57 +07:00 Verified
parent 227ef61e9d
commit 97b0f5b052
2 changed files with 38 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/current_roadmap.md
+4 -5
View File
@@ -113,11 +113,10 @@ auth admin are implemented. The next work is polish, not new broad surfaces.
- Completed source provider docs: `docs/source_provider_guide.md` now covers
MCP HTTP, MCP stdio, Python sources, auth refs, OAuth refresh-token setup,
diagnostics, and the Google Drive MCP caveat.
- Next design work: distinguish platform capability sources from external
source providers with metadata/policy on `CapabilitySource`. `wf.*` sources
such as `wf.std`, `wf.admin`, `wf.recipes`, and future `wf.source` should be
process-provided platform sources, not account-bound source bindings.
- Next design work after platform source policy: add `wf.source` helper
- Completed platform source policy: `wf.*` process-provided sources are marked
as platform sources and no longer require self-bindings such as
`wf.std=wf.std` in deployments.
- Next design work: add `wf.source` helper
capabilities for source-bound refs. Resource/prompt refs should be inert
pass-by-value data using `logical_source`; only explicit source-aware nodes
should dereference them through runtime/platform context.