Backend resource · STATIC DECLARATIONS

Setup Governance API reference · mansoq-core

Static source contract for Setup Governance: 3 declared or inherited operation mappings, schema/field evidence and authorization/refusal references. Deployment and behavioral review remain explicit.

Static API contract — behavior review pending. Source baseline f6e9f05f76d4.

Enable JavaScript to inspect structured operation, parameter, schema and permission evidence. Download this reference and its evidence.

Declared route and availability

This resource is declared in mansoq-core at /api/v1/facility/{facility_external_id}/rcm/setup_governance/. verified core mount in config/urls.py A registered path and an indexed handler do not prove deployment availability, user permission or production readiness.

Operation map

Method	Path	Action	Evidence
GET	`/api/v1/facility/{facility_external_id}/rcm/setup_governance/`	list	declared/inherited method
POST	`/api/v1/facility/{facility_external_id}/rcm/setup_governance/`	create	declared/inherited method
GET	`/api/v1/facility/{facility_external_id}/rcm/setup_governance/{external_id}/`	retrieve	declared/inherited method

list · GET

GET /api/v1/facility/{facility_external_id}/rcm/setup_governance/ — action list. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Location	Parameter	Type	Required
path	facility_external_id	router lookup string; semantic ID validation requires handler/schema review	true

Directly observed request reads (these do not constitute a complete accepted-payload or requiredness guarantee):

Location	Field	Declared/inferred read type	Requiredness evidence
query	`{computed field name}`	not declared at read site	not established
query	`effective_on`	not declared at read site	not established

Observed authorization checks: can_read_rcm_configuration_in_facility. Helper/queryset evidence is included; this is not proof of complete security review.

Declared refusal/error evidence: PermissionDenied: Cannot read RCM configuration.

create · POST

POST /api/v1/facility/{facility_external_id}/rcm/setup_governance/ — action create. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Location	Parameter	Type	Required
path	facility_external_id	router lookup string; semantic ID validation requires handler/schema review	true

Directly observed request reads (these do not constitute a complete accepted-payload or requiredness guarantee):

Location	Field	Declared/inferred read type	Requiredness evidence
body	`decision_reason`	not declared at read site	not established
body	`mode`	not declared at read site	direct indexing; validation may be upstream
body	`mfa_code`	not declared at read site	not established
body	`lock_token`	not declared at read site	not established
query	`{computed field name}`	not declared at read site	not established
query	`effective_on`	not declared at read site	not established

Observed authorization checks: can_publish_rcm_configuration_in_facility, can_read_rcm_configuration_in_facility. Helper/queryset evidence is included; this is not proof of complete security review.

Explicit response statuses in observed code: 409. Other branches/framework exception handling may differ.

Declared refusal/error evidence: PermissionDenied: Only the initiating owner can choose setup responsibilities; ValidationError: Setup governance fields are invalid; ValidationError (dynamic detail; inspect source); ValidationError: A first setup decision has no earlier lock token; PermissionDenied: Cannot approve, activate or publish RCM configuration; PermissionDenied: Cannot read RCM configuration.

retrieve · GET

GET /api/v1/facility/{facility_external_id}/rcm/setup_governance/{external_id}/ — action retrieve. static contract extracted; runtime/permission/payload behavior review pending.

Path and deployment-context parameters:

Location	Parameter	Type	Required
path	facility_external_id	router lookup string; semantic ID validation requires handler/schema review	true
path	external_id	router lookup string; semantic ID validation requires handler/schema review	true

Directly observed request reads (these do not constitute a complete accepted-payload or requiredness guarantee):

Location	Field	Declared/inferred read type	Requiredness evidence
query	`{computed field name}`	not declared at read site	not established
query	`effective_on`	not declared at read site	not established
query	`as_of`	not declared at read site	not established

Observed authorization checks: can_read_rcm_configuration_in_facility. Helper/queryset evidence is included; this is not proof of complete security review.

Declared refusal/error evidence: PermissionDenied: Cannot read RCM configuration.

Integration review checklist

Confirm the installed route and full schema; review authentication, organization/facility scoping, all accepted fields, value-state and date/time semantics, idempotency, pagination, response/exception branches and the allowed correction/reversal workflow. Test positive and negative cases with synthetic data. This source reference does not establish external certification or replace an illustrated user procedure.

Pinned source evidence

Links require access to the private source repository.