Jordan-Hall / Jordan-Hall/browser
[P2][SDK-02] SDKs, simulator and developer tools
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Programme: #1
Epic: #32
## Objective
Make connectors, UI components, agent/model adapters and workflow recipes buildable/testable by developers without requiring broad live credentials or reverse-engineering internal runtime state.
## Scope
- Rust SDKs for contracts/connectors/agent/model adapters.
- TypeScript/schema bindings where appropriate for extension/UI authoring.
- Local simulator with EVAL-01 services, fake accounts, clocks and resettable state.
- Manifest/schema validator and compatibility checker.
- Trace viewer, task graph inspector, policy/grant debugger, semantic-data/evidence inspector and connector explorer.
- Protocol recording/replay tooling for supported provider adapters.
- Template/reference packages and CI integration.
- Versioned developer documentation and migration guides.
## Product rules
- Local development should not require production credentials for core conformance testing.
- Devtools expose policy decisions/evidence/state, not private model chain-of-thought.
- Generated test fixtures cannot accidentally route to production endpoints.
## Acceptance criteria
- [ ] New connector/package can be developed and fully contract-tested against local fixtures.
- [ ] SDK versions detect incompatible runtime/schema versions early.
- [ ] Policy debugger explains allow/deny decisions using stable reason codes.
- [ ] Trace viewer reconstructs tasks/actions/evidence without replaying live side effects.
- [ ] Reference agent adapter can run a golden session in the simulator.
- [ ] CI templates validate manifests, schemas, security limits and fixtures.
## Dependencies
- CONN-01
- AGENT-02
- UI-01
- EVAL-01
**First phase:** P2
**Maturity target:** P6
**Owner:** platform
Contributor guide
No contributing guide indexed for this repository
Research direction
No implementation files or tests are named. Start by reading dependencies CONN-01, AGENT-02, UI-01, and EVAL-01, then narrow the work to one acceptance criterion and identify its owning package or entry point. Done requires a focused implementation that can be validated against the corresponding criterion without production credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- developer-experience, devtools, documentation, testing, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100