Monorepo workspace for the Softprobe Hybrid platform: proxy-first HTTP capture and replay, OTEL-shaped case artifacts, and a language-neutral control plane for rules and sessions.
| Path | Description |
|---|---|
spec/ |
Canonical contracts: schemas, protocols, and examples; product design lives in docs/design.md. |
softprobe-proxy/ |
Envoy/WASM data plane (Rust): HTTP client to runtime for inject/extract per spec/protocol/proxy-otel-api.md. |
softprobe-runtime (see tasks.md P0.0) |
OSS HTTP control API only (spec/protocol/http-control-api.md). Inject/extract: proxy backend (e.g. https://o.softprobe.ai). |
softprobe-js/ |
JavaScript SDK, codegen, optional temporary reference runtime. |
- Hybrid product and engineering design:
docs/design.md - Platform overview:
docs/platform-architecture.md - Repo topology:
docs/repo-layout.md
- HTTP control API — sessions, cases, rules (JSON)
- Proxy OTEL API — inject lookup and trace extract (protobuf)
- Session headers
This monorepo previously used separate Git repositories under proxy/ and softprobe-js/. Their .git directories were moved to .nested-git-backup/ (ignored by Git) so one repository could track the whole workspace. To work with the old remotes again, move the backup back, for example:
mv .nested-git-backup/proxy.git proxy/.git
Implementations should validate behavior against spec schemas and compatibility fixtures as they are added. Prefer extending the spec before changing proxy or SDK behavior in incompatible ways.