docs.rs failed to build clawft-platform-0.2.1
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
clawft-platform-0.1.1
Platform abstraction layer for clawft.
Provides traits for all platform-dependent operations (HTTP, filesystem, environment, process spawning) so the core engine can be platform-agnostic and WASM-compatible.
Architecture
The [Platform] trait bundles all platform capabilities via accessor methods.
Each sub-capability has its own trait ([http::HttpClient], [fs::FileSystem],
[env::Environment], [process::ProcessSpawner]) with a corresponding native
implementation.
ProcessSpawner is intentionally excluded from the
[Platform] bundle because it is unavailable in WASM environments. It is
accessible via [Platform::process] which returns Option.
Example
use ;
use HttpClient;
use HashMap;
# async
Crate Ecosystem
WeftOS is built from these crates:
| Crate | Role |
|---|---|
weftos |
Product facade -- re-exports kernel, core, types |
clawft-kernel |
Kernel: processes, services, governance, mesh, ExoChain |
clawft-core |
Agent framework: pipeline, context, tools, skills |
clawft-types |
Shared type definitions |
clawft-platform |
Platform abstraction (native/WASM/browser) |
clawft-plugin |
Plugin SDK for tools, channels, and extensions |
clawft-llm |
LLM provider abstraction (11 providers + local) |
exo-resource-tree |
Hierarchical resource namespace with Merkle integrity |