This is the shared knowledge base of LSI Media and CommunityForce: the place where we write down how we build and run AI services, the business models we use, why we made the choices we did, and what we’ve learned from our reading. It follows the rule both teams work by: process first, then AI, with people in charge.
| LSI Media | CommunityForce | |
|---|---|---|
| What it does | Digital media and AI automation for nonprofits, community foundations, credit unions, schools and government contractors | AI-powered awards management for grants, scholarships, fellowships and research funding, built for federal agencies, universities and foundations |
| Website | lsi-media.com | communityforce.com |
| What it brings here | Service playbooks, the GEO Engine, automation practice | Grants and awards domain knowledge, platform practice |
How it’s organized
| Collection | What goes in it | Title pattern |
|---|---|---|
| GEO Engine Guide | The build-and-run guide for the AI-visibility service engine, in parts | "Part X: …" |
| GEO Engine Skills | One article per procedure Claude follows | "Skill: Name (skill-slug)" |
| Playbooks | Business and service models we can run, step by step, including the SBIR/STTR Capture Playbook (a set of pages with its own menu) | "Playbook: …" |
| Research & Decisions | Source notes and the reasoning behind choices | "Video Notes: …", "Decision: …" |
| Book Notes | Our own summaries of books in the library, by subject | "Book Notes: Title (Author)" |
| BMA Portfolio Field Guide | Onboarding guide to the DAF Business Mission Area portfolios, with system index, system cards and SPHERE cloud roster | One interactive page, as in the original |
| C1FAMS Knowledge Base | Cloud One FAMS and access management: videos with transcripts, how-to articles, FAQ, glossary, resources | Page tree with the original menu: Videos, Articles, FAQ, Glossary, Resources, Search |
Tags cut across collections (for example telegram, onboarding, costs). Search covers everything you have access to.
Who can read what
Articles are private: only logged-in administrators and editors can read them. The home page, this page and the collection pages are public but show no private content to visitors. To share an article publicly, change its visibility to Public in the editor (Post → Status → Public). Check it for personal details first.
Never put CommunityForce customer data, real prospect names, or client records in any article, private or public. Use made-up examples instead.
Adding an article
- Posts → Add New Post. Use the title pattern for its collection.
- Choose one collection (category) and a few tags.
- Write a one-sentence excerpt: it appears in lists and search results.
- Lead with the answer; use headings that match the questions people will ask; link related articles.
- Set visibility to Private unless it’s meant for the public.
- For book notes: summarize in your own words, keep any quotation under 15 words, and never upload the book itself.
- For anything health- or finance-related: label it as reference, not advice.
Keeping it current
- Each article states its source (a file, a repo, a video) so it can be checked.
- When the source changes (for example
GUIDE.mdin the geo-engine repo), update the source first, then the article. - Review the collections quarterly: merge duplicates, retire what’s out of date, and fill gaps.
Maintained by
Idris Grant, for LSI Media LLC and CommunityForce.