alknet/tasks/architecture/spec-update-napi.md at 835724d08748d50390553c69df04a664043a8397

Files

glm-5.1 84f16d66e7 tasks: decompose Phase 0b spec documents and Phase 0c review

Add 15 new tasks under tasks/architecture/ for Phase 0b (spec writing)
and Phase 0c (review):

Phase 0b — New specs (6):
  - spec-configuration: promote from research, cleanup, align with ADRs
  - spec-identity: carry from auth.md + services.md, canonical Identity
  - spec-secret-service: from research/services.md SecretProtocol
  - spec-storage: from research/storage.md, contract-level
  - spec-flowgraph: from research/flow.md, pure computation crate
  - spec-interface: new Layer 2 spec (highest risk new spec)
  - spec-services: irpc service layer + OperationEnv (broadest scope)

Phase 0b — Spec updates (6):
  - spec-update-overview: add crate structure, Layer 3, services
  - spec-update-auth: IdentityProvider vs AuthService relationship
  - spec-update-call-protocol: OperationEnv dispatch paths
  - spec-update-server: DynamicConfig, ForwardingPolicy, IdentityProvider
  - spec-update-napi: reload API, call protocol references
  - spec-update-open-questions: resolve OQs per ADR decisions

Phase 0b — Assembly (1):
  - spec-update-readme: add new docs and ADRs to tables

Phase 0c — Review (1):
  - review-spec-foundation: validate consistency checklist

Generation structure (6 total):
  Gen 1: 6 independent ADRs (parallel)
  Gen 2: adr-027, adr-028 (depend on adr-029)
  Gen 3: adr-033 + 6 spec docs + open-questions update (parallel)
  Gen 4: adr review + interface/services specs + 4 spec updates
  Gen 5: call-protocol update + readme update
  Gen 6: spec review

2026-06-07 09:01:01 +00:00

1.9 KiB

Raw Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

architecture/spec-update-napi

Update napi-and-pubsub.md — add reload API and call protocol references

pending

architecture/spec-configuration

architecture/adr-033-operationenv-irpc-call-protocol

narrow

low

component

implementation

Description

Update docs/architecture/napi-and-pubsub.md to add the NAPI reload API (reloadAuth, reloadForwarding, reloadAll) and references to the call protocol integration.

The current spec is reviewed and stable. Changes are additive:

Add reloadAuth(), reloadForwarding(), reloadAll() methods to AlknetServer interface
Add note about call protocol integration: NAPI consumers can register operation handlers
Add note about irpc service creation for NAPI consumers (behind feature flag)
Reference configuration.md and services.md for details

What stays the same: Everything else. The NAPI wrapper, pubsub adapter, connect vs serve semantics, stream handling, constraints — all unchanged.

Acceptance Criteria

AlknetServer interface in NAPI section updated with reloadAuth(), reloadForwarding(), reloadAll()
TypeScript interface signature for reload methods matches research/configuration.md NAPI section
Note added: call protocol integration — NAPI consumers can register operation handlers
Note added: irpc service creation available for NAPI consumers (feature-gated)
References to configuration.md and services.md added
last_updated in YAML frontmatter updated
Existing content unchanged except where additions are made
ADR references remain correct

References

docs/architecture/napi-and-pubsub.md — current content
docs/research/configuration.md — NAPI Reload API section
docs/research/integration-plan.md — Phase 3.4 (NAPI layer updates)

Notes

To be filled by implementation agent

Summary

To be filled on completion

1.9 KiB Raw Blame History