records, outbox, lifecycle requests, relay, push, read-back, and FedWiki
lifecycle workflows
- Add core.provider_connections table and unique provider connection per
provider
- Add core.target_mappings table linking connections to resource keys
and targets
- Add core.desired_state_records table storing desired entitlements per
connection and recipient with generation and content hash
- Add core.observed_projections table for application-reported state per
connection and recipient
- Add core.lifecycle_requests table recording lifecycle requests by
instance and generation
- Add core.person_cut_offs table and setter function to record persons
cut off everywhere
- Add core.desired_state_outbox table with triggers on entitlement,
membership, organization, connection, mapping, and cut-off tables to
write change notices
- Enforce constraints on recipients, generations, and statuses across
tables
- Implement desired_state_content SQL function computing record content
per recipient rules
- Implement relay workflow to claim outbox rows, expand to records,
recompute records, and dispatch pushes
- Implement push workflow to push records, handle transport answers, and
record push results
- Implement read-back workflow to page through application state, update
projections, and raise records as needed
- Add lifecycle request writers with idempotent recording, finishing,
and acknowledgment
- Add FedWiki integration lifecycle workflows for create, set status,
swap, delete, and reconcile
- Add FedWiki web handlers and forms for lifecycle requests, including
create form with instance and generation
- Add tests for schema, triggers, relay, push, read-back, lifecycle
requests, FedWiki workflows, and operator pages
- Add documentation updates for provider integration, entitlements,
identity, organizations, lifecycle, and FedWiki integration
- Add benchmarks for delivery and push workflows
- Ensure schema-per-provider for in-tree integrations; connector state
lives in generic core tables keyed by connection
- Secure functions and triggers with SECURITY DEFINER and restrict
core_writer role privileges accordingly
- Handle Temporal client integration for workflow execution and
scheduling
- Provide a recording transport for integration tests
- Close Issues 32 and 33 by implementing provider connections and
desired-state records with lifecycle requests and relay mechanisms
cgalo5758
23d5bad024