resource-request

Structured resource requests within governance pools require capturing requester identity, resource type, amount, funding pool target, and rationale to separate requesting from approving. This creates a transparent intake pipeline tying every decision to ecosystem purpose while preventing self-dealing.

A formal stewardship and consent workflow applies to financial, physical, time, access, and expertise needs across circles and pools. It supports cross-domain routing, emergency workflows, and standing agreements while recording ACT routing levels and decision records for auditable governance.

To start an auditable resource request, fill out the resource-request-template.yaml with required fields including requester identity, resource type, amount, funding pool target, rationale, timeline, stewardship commitment, and domain scope, then submit it through your circle's governance channel.

A structured funding pool request system supports cross-circle routing and emergency workflows through ACT-oriented governance. It applies adviser, consent, and integration steps across domains while maintaining standing agreements and recording fulfillment status and review dates.

Tracking funding pool fulfillment status and decision records requires capturing required inputs at request inception and recording ACT routing level, decision records, fulfillment status, and review dates throughout the workflow, ensuring every approval ties to ecosystem purpose for auditable governance.