alknet

alkdev/alknet

Fork 0

Commit Graph

Author	SHA1	Message	Date
glm-5.1	3a046546d4	Restructure integration plan: insert Phase 2 Core Bridge, renumber phases - New Phase 2 (Core Bridge): SshSession recv/send, RawFramingInterface, StreamInterface/MessageInterface split, CredentialProvider trait, HTTP listener stub, API keys, axum scaffold - Old Phase 2 (External Crates) → Phase 3 - Old Phase 3 (Integration) → Phase 4 (now includes doc sync) - Old Phase 4 (Advanced) → Phase 5 (now includes full HTTP, git service) - Updated open questions: resolved Phase 0/1 items, added Phase 2 OQs - Updated inconsistencies: added items 8-11 (interface split, SshSession stubs, CredentialProvider gap, doc sync need)	2026-06-09 05:18:29 +00:00
glm-5.1	6db1266672	docs: fix inconsistencies in architecture specs - Replace hub/spoke with head/worker terminology in call-protocol.md, auth.md, open-questions.md, napi-and-pubsub.md - Update operation paths from /{spoke}/{service}/{op} to /{node}/{service}/{op} throughout call-protocol.md - Unify Identity struct: auth.md already had {id, scopes, resources}, add note clarifying this is canonical (vs research/services.md which used {node_id, fingerprint, scopes}) - Update integration-plan.md inconsistencies section to track what's been fixed (hub/spoke, identity model) and expand service naming to include external services - Update call-protocol.md last_updated date ADRs are intentionally left unchanged as historical records.	2026-06-07 07:50:00 +00:00
glm-5.1	69d232fda7	docs: add integration plan for services, pubsub, and operations Organizes findings from the research phase (core, services, configuration, storage, flow) into an actionable phased plan covering: - Transport/Interface/Protocol three-layer model - OperationEnv as universal composition mechanism (not replaced by irpc) - Phase 0: Architecture foundation (9 ADRs, ~10 spec docs) - Phase 1: Core modifications (config split, identity, forwarding, auth, OperationEnv, interface abstraction) - Phase 2: External crates (alknet-secret, alknet-storage, alknet-flowgraph) - Phase 3: Integration and wiring - Phase 4: Advanced features (DNS, WebTransport, app services) Key clarifications: irpc services are one dispatch backend for OperationEnv, not a replacement for it. DNS control channel is a (DNS transport, raw framing interface) pair, not SSH-over-DNS. Call protocol and irpc operate at different scope boundaries within Layer 3.	2026-06-07 07:28:05 +00:00

Author

SHA1

Message

Date

glm-5.1

3a046546d4

Restructure integration plan: insert Phase 2 Core Bridge, renumber phases

- New Phase 2 (Core Bridge): SshSession recv/send, RawFramingInterface,
  StreamInterface/MessageInterface split, CredentialProvider trait,
  HTTP listener stub, API keys, axum scaffold
- Old Phase 2 (External Crates) → Phase 3
- Old Phase 3 (Integration) → Phase 4 (now includes doc sync)
- Old Phase 4 (Advanced) → Phase 5 (now includes full HTTP, git service)
- Updated open questions: resolved Phase 0/1 items, added Phase 2 OQs
- Updated inconsistencies: added items 8-11 (interface split, SshSession
  stubs, CredentialProvider gap, doc sync need)

2026-06-09 05:18:29 +00:00

glm-5.1

6db1266672

docs: fix inconsistencies in architecture specs

- Replace hub/spoke with head/worker terminology in call-protocol.md,
  auth.md, open-questions.md, napi-and-pubsub.md
- Update operation paths from /{spoke}/{service}/{op} to
  /{node}/{service}/{op} throughout call-protocol.md
- Unify Identity struct: auth.md already had {id, scopes, resources},
  add note clarifying this is canonical (vs research/services.md which
  used {node_id, fingerprint, scopes})
- Update integration-plan.md inconsistencies section to track what's
  been fixed (hub/spoke, identity model) and expand service naming
  to include external services
- Update call-protocol.md last_updated date

ADRs are intentionally left unchanged as historical records.

2026-06-07 07:50:00 +00:00

glm-5.1

69d232fda7

docs: add integration plan for services, pubsub, and operations

Organizes findings from the research phase (core, services, configuration,
storage, flow) into an actionable phased plan covering:

- Transport/Interface/Protocol three-layer model
- OperationEnv as universal composition mechanism (not replaced by irpc)
- Phase 0: Architecture foundation (9 ADRs, ~10 spec docs)
- Phase 1: Core modifications (config split, identity, forwarding, auth,
  OperationEnv, interface abstraction)
- Phase 2: External crates (alknet-secret, alknet-storage, alknet-flowgraph)
- Phase 3: Integration and wiring
- Phase 4: Advanced features (DNS, WebTransport, app services)

Key clarifications: irpc services are one dispatch backend for OperationEnv,
not a replacement for it. DNS control channel is a (DNS transport, raw framing
interface) pair, not SSH-over-DNS. Call protocol and irpc operate at different
scope boundaries within Layer 3.

2026-06-07 07:28:05 +00:00

3 Commits