## Sports clubs: member portal using Laravel

### Summary
A member portal blueprint for sports clubs built with Laravel on Ample. Domain schema: course_groups (team_or_class, season, age_group): teams and classes; memberships (course_group_id, member_reference, guardian_reference, role): players, guardians and coaches; sessions (course_group_id, starts_at, venue, type): training and fixtures; materials (course_group_id, title, object_key, visibility): schedules and coaching resources; document_access (document_id, principal_reference, role, granted_at): who may read which document. Public information: teams, seasons and fixtures, venues, membership fees. Kept out of scope until handling is reviewed: minor members and medical notes, safeguarding records. Medical and safeguarding records are sensitive; only schedules and coaching materials are modeled. 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
- Sports clubs: member portal using Laravel
- Where can I host Sports clubs: Member portal built with Laravel?
- I need a genuinely specialized member portal workflow covering team membership, event participation and club media.

### 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 sports clubs domain**: Create the tables course_groups, memberships, sessions, materials, document_access. Teams and classes live in course_groups; keep the sensitive classes (minor members and medical notes, safeguarding records) out of this schema.
2. **Workflow step 1**: Model groups, memberships and roles.
3. **Workflow step 2**: Authorize access to materials by membership and role (401, 403 negative tests).
4. **Workflow step 3**: Store materials in the private bucket and stream them through the app.
5. **Workflow step 4**: Deploy and verify the negative tests and an authorized download.
6. **Deploy**: Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
7. **Verify**: Run the pattern self-test(s) from the example (/p/private-document-library) and your own acceptance checks for the sports clubs workflow.

### Examples
- **Laravel pattern fixture**: Verified private document library basis for this blueprint.

### Limitations
- The technical basis (private document library on Laravel) was verified with the pattern fixture; the sports clubs 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. Medical and safeguarding records are sensitive; only schedules and coaching materials are modeled.
