### Nonprofits: member portal using Laravel

#### Summary
A member portal blueprint for nonprofits built with Laravel on Ample.

Domain schema:
- **course_groups** (program, cohort, start_at, end_at): programs and cohorts
- **memberships** (course_group_id, participant_reference, role): participants, volunteers, and staff
- **sessions** (course_group_id, starts_at, title, location): program sessions and events
- **materials** (course_group_id, title, object_key, visibility): program materials
- **document_access** (document_id, principal_reference, role, granted_at): who may read which document.

Public information: mission and programs, events, donation entry point.
Kept out of scope until handling is reviewed: beneficiary identity and case notes, donor records. 
Beneficiary and donor data are sensitive; donations are handled by your payment provider and are not modeled here.

Technical basis verified on Laravel: a role-to-document access model with negative tests (401 without identity, 403 for the wrong role) and a private-bucket round-trip for the allowed role (private=ok).

#### Representative Queries
- Nonprofits: member portal using Laravel
- Where can I host Nonprofits: Member portal built with Laravel?
- I need a genuinely specialized member portal workflow covering program participation, volunteer events, and program resources.

#### Resource Requirements
- **primitive:compute**
- **primitive:postgres**
- **primitive:s3-compatible-object-storage**

#### Infrastructure Requirements
1. **Compute**: Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
2. **Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.
3. **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

#### Workflow Steps
1. **Model the nonprofits domain**: Create the tables course_groups, memberships, sessions, materials, document_access. Programs and cohorts live in course_groups; keep the sensitive classes (beneficiary identity and case notes, donor records) out of this schema.
2. **Authorize access** to materials by membership and role (401, 403 negative tests).
3. **Store materials** in the private bucket and stream them through the app.
4. **Deploy** and verify the negative tests and an authorized download.
5. **Run the synchronous deploy once** and read the result. Re-running with no change is a no-op.
6. **Verify**: Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the nonprofits workflow.

#### Success Checks
1. App responds on its public URL: `/`, expect `ample canary laravel patterns`.
2. Private-document-library self-test from the example: `/p/private-document-library`, expect `see the pattern fixture checks`.

#### Limitations
- The technical basis (private document library on Laravel) was verified with the pattern fixture; the nonprofits schema and workflow are an original design for this blueprint and were not executed as a separate application.
- No health, financial, privacy, or other compliance claim is made. Beneficiary and donor data are sensitive; donations are handled by your payment provider and are not modeled here.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.

#### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Components**:
  - App server: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
  - Managed PostgreSQL database: s-1vcpu-1gb, Quantity: 1.0, Monthly Amount: 5.0
- **Note**: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

#### Examples
- **Title**: Laravel pattern fixture  
  **Description**: Verified private document library basis for this blueprint.  
  **Source Reference**: tests/deploy-canaries/laravel-patterns

#### Evidence Summary
The blueprint's Nonprofits schema and workflow build on the verified basis and were not separately executed.