Skip to content

San Francisco Fil-Am Lions Club Handbook

This handbook contains the club's currently documented operating procedures.

Roles

  • Treasurer — Zoho Invoice, dues, payments, reimbursements, bank statements, and check-register review.
  • Secretary — meeting agendas and minutes.
  • Marketing — club website and YouTube work.

AI Transparency and Usage

The San Francisco Fil-Am Lions Club Handbook is developed and maintained with the assistance of artificial intelligence (AI). AI tools help draft, organize, review, and improve documentation, with club officers responsible for reviewing and approving substantive changes.

The handbook is also designed to be used by AI assistants as a reference for supporting club officers in their administrative and operational workflows. These workflows may include preparing meeting agendas and minutes, maintaining membership records, reviewing financial information, and assisting with other documented club procedures.

AI assistance does not replace human judgment or authority. AI-generated information and proposed actions should be verified as appropriate. Actions requiring authorization—including financial transactions, external communications, and modifications to official records—must receive the necessary approval before execution.

The handbook provides procedural guidance; its contents do not independently authorize AI systems to act on behalf of the club.

Note: This is an internal handbook. The GitHub repository is the source of truth; GitHub Pages renders the same Markdown for reading.

Change History and releases

The Change History summarizes changes included in each published handbook release. For an exact record of individual edits, see the commits on GitHub.

The handbook site deploys after pushes to main. Separately, Release Please checks those pushes for releasable Conventional Commits and proposes a release pull request. A release is published only after its release PR is merged; not every website deployment creates a new version. Use feat: for substantial new capabilities and fix: for corrections that should trigger a release. Routine docs: edits appear in release notes when included with a releasable change, but do not normally trigger a release themselves with the simple release strategy. Human review remains required for publishing a release.