Architectural Decision Records¶

Each record states one decision about how redsun is built, in the format Michael Nygard describes: status, context, decision, consequences. An accepted record is never edited; a later one replaces it.

• 1. Record architecture decisions
• 2. Storage dual-context redesign (superseded by 13)
• 3. Structural subtyping for presenters and views
• 4. Owner-scoped signal lookup
• 5. Culsans-backed psygnal async backend
• 6. Application-declared wiring
• 7. Typed provider keys
• 8. Container hooks and the build phase registry
• 9. Inherited and layered component configuration
• 10. Toolkit hook points
• 11. Tolerating a component that fails to build
• 12. Services and two connection levels
• 13. Acquisition storage belongs to the device
• 14. Typed session files and plugin manifests
• 15. Collaborators arrive in setup
• 16. A component refused at declaration is skipped
• 17. Questions read from the annotation
• 18. Wire yields links
• 19. Copy plan progress from bluesky
• 20. A built-in positioner
• 21. A built-in light stack
• 22. A built-in acquisition stack
• 23. Pairing two components
• 24. A plan widget for every parameter type it can return
• 25. A view's placement chosen per declaration
• 26. Parameter limits from annotated-types, checked by pydantic