feat(identity): stage 1.2 — POST /capabilities/request step-up auth endpoint spec #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "mark/stage-1-2-identity"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds the endpoint spec for
POST /capabilities/request— the JIT capability step-up API from Stage 1.2.This endpoint is the server-side counterpart to
CapabilityClient.swift(Rituals macOS PR #122). It resolves an actor's capability grant status and either returns a short-lived Vault token or a Keycloak step-up challenge URL.See
docs/capabilities-request.mdfor the full request/response shapes, auth flow, and error codes.Related
CapabilityClientSwift implementationcore.capability_scopes+core.actor_identity_bindingsmigrations that back this endpointAdds the Phase 2 resource-broker contract: a new ForgeBlock discriminant for compute/event-stream resources, plus REST paths for managing them. All changes are additive — existing block types, oneOf order, and discriminator mappings are preserved. schemas/forge_block.json: * ResourceBlock variant (kind: mlx_model | kafka_topic | kafka_consumer | tier_policy) with handle/title/health/metrics/actions * ResourceKind, ResourceHealth, ResourceMetric supporting types * ForgeBlock.oneOf and discriminator.mapping extended with "resource" openapi.yaml: * frame_type enum gains "resource_allocation" * ResourceBlock + supporting schemas mirrored under components.schemas * ForgeBlock oneOf/discriminator extended in parallel * 6 new path operations under /resources/{mlx-models, mlx-models/{handle}, kafka-topics, kafka-consumers, kafka-consumers/{group_id}, tier-policy} * new "resources" tag Validates: 50 paths, 63 schemas, all $refs resolve, discriminator coverage complete. The TS client at rituals-chat/packages/channel-adapter mirrors these definitions; once this lands the client regenerates from the canonical schema via json-schema-to-typescript.New endpoints for universal entity blocks: - GET /{entity_type}/{entity_id}/blocks - render entity detail blocks - GET /{entity_type} - list entity blocks with pagination - GET /wishes/active, /wishes/active/hydration-needs, /wishes/active/hydrate - POST /wishes/groom-queue/{id}/review - triage backlog items - GET /wishes/groom-queue - browse pending backlog - POST /ruses/{id}/invoke - execute ruse - GET /lineage/{id}/graph - ancestry/descendant graph Supports multiple rendering surfaces (web, flutter, macos) via spec and surface query params. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>