Thanks to visit codestin.com
Credit goes to github.com

Skip to content

RFC: lifecycle, kernel management, system, and hook bridge event contracts - #15

Closed
joshuajbouw wants to merge 1 commit into
mainfrom
rfc/hook-lifecycle-protocol
Closed

joshuajbouw wants to merge 1 commit into
mainfrom
rfc/hook-lifecycle-protocol

Conversation

@joshuajbouw

@joshuajbouw joshuajbouw commented Mar 16, 2026

Copy link
Copy Markdown
Member

Event contract RFCs for kernel infrastructure and observability:

  • 0000-lifecycle-v1-events.md - all 42+ lifecycle event types with metadata schema (astrid.v1.lifecycle.*)
  • 0000-kernel-management-v1-events.md - management API request/response (astrid.v1.request.*, astrid.v1.response.*)
  • 0000-system-v1-events.md - capsules_loaded, watchdog, health, bus lag, client connect (system.v1.*, client.v1.*)
  • 0000-hook-bridge-v1-events.md - lifecycle-to-hook translation (hook.v1.*)

Each RFC specifies topic patterns, message schemas, behavioral requirements, and error handling.

@joshuajbouw
joshuajbouw force-pushed the rfc/hook-lifecycle-protocol branch 2 times, most recently from 670cd71 to 3133aa1 Compare March 16, 2026 14:36
…tract RFCs

Replaces the capsule-centric hook lifecycle RFC with four granular
event contract specifications:

- lifecycle.v1 events: all 42+ lifecycle event types with metadata schema
- kernel management events: astrid.v1.request/response management API
- system events: capsules_loaded, watchdog, health, bus lag, client connect
- hook bridge events: lifecycle-to-hook translation and result publishing

Each RFC specifies topic patterns, message schemas, behavioral
requirements, and error handling for its namespace.
@joshuajbouw
joshuajbouw force-pushed the rfc/hook-lifecycle-protocol branch from 3133aa1 to 372531e Compare March 16, 2026 16:36
@joshuajbouw joshuajbouw changed the title RFC: Hook lifecycle protocol RFC: lifecycle, kernel management, system, and hook bridge event contracts Mar 16, 2026
@joshuajbouw

Copy link
Copy Markdown
Member Author

Closing — the design evolved significantly during v0.5.0 implementation. The provides/requires model was replaced by [imports]/[exports] with semver, WIT interfaces became the spec format, and export conflict detection replaced the supersedes concept. New RFCs reflecting what was actually built will replace these.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant