alknet

alkdev/alknet

Fork 0

Commit Graph

Author	SHA1	Message	Date
glm-5.1	6219a323b6	docs(architecture): untangle TLS identity use cases, remove phase framing, add ADR-013 Rust canonical + agent crate - Rewrite OQ-12: separate two distinct TLS identity use cases (RFC 7250 raw keys as default for P2P, X.509 for domain-hosted/browsers) instead of conflating them as 'file paths now, ACME later'. ACME is a proven pattern from the reverse-proxy project, not speculative future work. - Resolve OQ-13 and OQ-14: remove 'Phase 1' framing from core crate specs. /{service}/{op} is the correct design for alknet-call, not a simplification. Batch as correlated call.requested events is the correct protocol design. Core crates need to be done right from the start. - Add ADR-013: Rust as canonical implementation language. TypeScript @alkdev/operations is a reference that informed the design, not a parallel implementation. The only JS use case is browser SDK adaptation. Five reasons: memory safety, LLM competence, supply chain attacks, performance, browser-only JS. - Add alknet-agent crate to the crate graph (depends on alknet-call, not alknet-core). Agent service uses call protocol client for tool dispatch and vault/derive for provider keys — no env vars for secrets. ALPN alknet/agent added to the registry. - Add OQ-15: call protocol client and adapter contract. alknet-call needs both server (CallAdapter) and client (remote invocation over QUIC), plus the adapter traits (from_, to_) that enable composition. - Clarify alknet-napi as thin NAPI projection layer, not business logic. - Fix bugs: ProtocolController → ProtocolHandler typo, OperationEnv invoke() path format inconsistency, RateLimitConfig comment confusion. - Update endpoint.md TLS section: comprehensive identity model comparison table, RFC 7250 as default mode, ACME as proven pattern.	2026-06-17 09:32:44 +00:00
glm-5.1	90d5f4eaf9	docs(architecture): spec alknet-core with per-crate subdocs, ADR-010/011 Add alknet-core architecture specs in docs/architecture/crates/core/ with focused subdocuments for core types, endpoint, auth, and config. Write ADR-010 (ALPN Router and Endpoint) defining AlknetEndpoint, HandlerRegistry, accept loop, and graceful shutdown. Write ADR-011 (AuthContext Structure) defining AuthContext fields, immutability in handle(), and IdentityProvider injection pattern. Resolve OQ-04 (static registration), OQ-12 (file paths only for v1). Add OQ-11 (auth observability). Fix remaining alknet-secret references to alknet-vault across ADRs 003/004/005/009.	2026-06-16 12:07:17 +00:00
glm-5.1	f77b515968	docs(architecture): add Phase 0 architecture specs for ALPN-as-service model Foundational architecture documents following the SDD process: ADRs: - 001: ALPN-based protocol dispatch (one endpoint, ALPN negotiation) - 002: ProtocolHandler trait (replaces StreamInterface/MessageInterface) - 003: Crate decomposition (one crate per handler, core provides shared infra) - 004: Auth as shared core (IdentityProvider, hybrid resolution model) - 005: irpc as call protocol foundation - 006: ALPN string convention and connection model (alknet/ prefix, one ALPN per connection) Docs: - overview.md: crate graph, shared types, ALPN registry, failure modes - README.md: index with doc table, ADR table, lifecycle definitions - open-questions.md: 10 OQs across 7 themes (3 resolved, 7 open) Crate spec stubs for all 11 planned crates (alknet-core through alknet CLI). Key decisions resolved during self-review: - AuthContext resolution is hybrid: endpoint resolves TLS-level auth, handlers resolve protocol-level auth (resolves OQ-02) - ALPN is per-connection not per-stream, corrected ADR-001 (resolves OQ-06) - ALPN naming uses alknet/ prefix without versions (resolves OQ-03) - HandlerError return type on ProtocolHandler trait - alknet/secret removed from ALPN registry until OQ-08 resolved	2026-06-15 22:14:58 +00:00

Author

SHA1

Message

Date

glm-5.1

6219a323b6

docs(architecture): untangle TLS identity use cases, remove phase framing, add ADR-013 Rust canonical + agent crate

- Rewrite OQ-12: separate two distinct TLS identity use cases (RFC 7250
  raw keys as default for P2P, X.509 for domain-hosted/browsers) instead
  of conflating them as 'file paths now, ACME later'. ACME is a proven
  pattern from the reverse-proxy project, not speculative future work.

- Resolve OQ-13 and OQ-14: remove 'Phase 1' framing from core crate
  specs. /{service}/{op} is the correct design for alknet-call, not a
  simplification. Batch as correlated call.requested events is the correct
  protocol design. Core crates need to be done right from the start.

- Add ADR-013: Rust as canonical implementation language. TypeScript
  @alkdev/operations is a reference that informed the design, not a
  parallel implementation. The only JS use case is browser SDK adaptation.
  Five reasons: memory safety, LLM competence, supply chain attacks,
  performance, browser-only JS.

- Add alknet-agent crate to the crate graph (depends on alknet-call, not
  alknet-core). Agent service uses call protocol client for tool dispatch
  and vault/derive for provider keys — no env vars for secrets. ALPN
  alknet/agent added to the registry.

- Add OQ-15: call protocol client and adapter contract. alknet-call needs
  both server (CallAdapter) and client (remote invocation over QUIC), plus
  the adapter traits (from_*, to_*) that enable composition.

- Clarify alknet-napi as thin NAPI projection layer, not business logic.

- Fix bugs: ProtocolController → ProtocolHandler typo, OperationEnv
  invoke() path format inconsistency, RateLimitConfig comment confusion.

- Update endpoint.md TLS section: comprehensive identity model comparison
  table, RFC 7250 as default mode, ACME as proven pattern.

2026-06-17 09:32:44 +00:00

glm-5.1

90d5f4eaf9

docs(architecture): spec alknet-core with per-crate subdocs, ADR-010/011

Add alknet-core architecture specs in docs/architecture/crates/core/ with
focused subdocuments for core types, endpoint, auth, and config. Write
ADR-010 (ALPN Router and Endpoint) defining AlknetEndpoint, HandlerRegistry,
accept loop, and graceful shutdown. Write ADR-011 (AuthContext Structure)
defining AuthContext fields, immutability in handle(), and IdentityProvider
injection pattern. Resolve OQ-04 (static registration), OQ-12 (file paths
only for v1). Add OQ-11 (auth observability). Fix remaining alknet-secret
references to alknet-vault across ADRs 003/004/005/009.

2026-06-16 12:07:17 +00:00

glm-5.1

f77b515968

docs(architecture): add Phase 0 architecture specs for ALPN-as-service model

Foundational architecture documents following the SDD process:

ADRs:
- 001: ALPN-based protocol dispatch (one endpoint, ALPN negotiation)
- 002: ProtocolHandler trait (replaces StreamInterface/MessageInterface)
- 003: Crate decomposition (one crate per handler, core provides shared infra)
- 004: Auth as shared core (IdentityProvider, hybrid resolution model)
- 005: irpc as call protocol foundation
- 006: ALPN string convention and connection model (alknet/ prefix, one ALPN per connection)

Docs:
- overview.md: crate graph, shared types, ALPN registry, failure modes
- README.md: index with doc table, ADR table, lifecycle definitions
- open-questions.md: 10 OQs across 7 themes (3 resolved, 7 open)

Crate spec stubs for all 11 planned crates (alknet-core through alknet CLI).

Key decisions resolved during self-review:
- AuthContext resolution is hybrid: endpoint resolves TLS-level auth,
  handlers resolve protocol-level auth (resolves OQ-02)
- ALPN is per-connection not per-stream, corrected ADR-001 (resolves OQ-06)
- ALPN naming uses alknet/ prefix without versions (resolves OQ-03)
- HandlerError return type on ProtocolHandler trait
- alknet/secret removed from ALPN registry until OQ-08 resolved

2026-06-15 22:14:58 +00:00

3 Commits