A quick look at what we're building. One platform, a fleet of microservices, one team. Each page covers a service: what it is, what it replaces (or whether it's brand new), and how it connects to the rest. Status chips tell the truth. Live is deployed, In Build is under construction, Boarding is scoped and crewed.

Geauxjüre is a massive expansion of SAB, the Scripture App Builder, the longtime standard for building Scripture apps. It turns FCBH's Bible Brain catalog (~3,349 Bibles across ~2,306 languages) into finished, branded apps. Three doors in, one rights gate, zero developers required.

• PWA BuilderCompose a full progressive web app (reader, audio player, offline support) from catalog content.
• SAB ImportBring an existing Scripture App Builder project in and modernize it without starting over.
• YouTube ToolSegment and publish Scripture audio to YouTube playlists, timed and titled automatically.
• Rights built inThe Bible Brain key is the sole rights gate: if content clears the key, it's cleared to ship.

Enterprise ticketing in its own service, replacing our helpdesk tools and facilities ticketing alike. Ten queues, one catalog, real SLAs, every requester heard.

• 10 queues, 40-item catalogFrom password resets to room setups: pick, fill, submit in three steps.
• Real SLAsP1 IT response in 15 minutes. Field ops in 30. Tracked per queue, per priority.
• RBAC done right6 roles, 28 permissions, area-of-responsibility scoping, 4 technician teams.
• Template builderDepartment leads design their own ticket forms with live preview, no dev ticket needed.
• Knowledge base8 categories, self-serve answers before a ticket ever gets filed.
• Reports that exportKPI dashboards with CSV / Markdown / JSON export for the board pack.

Every app in Battlefield throws off tasks: a Pulse ticket, an Archangel email you clipped, a notetaker action item, a Helpdesk request. Quill is the single thread that holds them all: one to-do fabric, embeddable everywhere, with a line back to wherever each task was born.

• One store, every appA central task spine on shared infrastructure, no per-service silos to reconcile.
• Clip from anywhereArchangel mail, Pulse messages, Helpdesk tickets land as tasks with a deep link home.
• Provenance built inEvery task remembers its origin and jumps you straight back to the source.
• Guarded write-doorExternal and AI producers stamp trust and de-dupe, nothing double-files.
• Proposed vs. promotedAI-suggested tasks stay owner-only until a human promotes them.
• Cmd-K quick addCapture a task from any screen without leaving what you're doing.

Today /donor is a working placeholder: pipeline, campaigns, and a full events workspace. The build target is bigger: a custom CRM modeled on what the Donor Services team actually does, replacing the need for Salesforce seats with something shaped exactly like FCBH's donor work.

• Donor pipelineStage-by-stage cultivation view: who's warming, who's ready, who needs a call this week.
• Campaign trackingAppeals and initiatives with progress against goal, side by side.
• Events workspaceFull RSVP management: invitations, responses, seating, follow-ups.
• The custom modelDesigned with Donor Services, not sold to them; every object in the schema earns its place.

FCBH signs a lot of paper: contracts, ICAs, releases. Vault covers the whole path, from preparing a document to filing the signed copy in the same archive it will live in.

• PrepareA tagging wizard drops signature, date, and text fields onto any document.
• Sign and returnInternal signers draw or type their signature and send it back in the browser.
• External by linkOutside parties review, request changes, sign, and download. No login, just a link.
• Filed on completionEvery completed document lands in the archive automatically; signing never waits on it.
• Embeddable by moduleTagged for Finance, Field, Office, and IP, so each folds signing into its own flow.
• One product, honestlyE-sign started as its own service, Seal, and was folded into Vault: one archive that signs, instead of two tools handing off.

The All Access Goals set the bar for Scripture access in every language. Language Master is the gold standard for language data, and it replaced Monday.com as the place that data lives: percent complete per language, and a clear flag for when we vary from the All Access Goals, and when we don't.

• Percent-complete gaugeEvery language scored against its All Access Goal, at a glance.
• Variance flagsWhere we deviate from AAG on purpose, and where we've drifted: named, not buried.
• Canonical registryOne authoritative entry per language; every other service defers to its IDs.
• Catalog alignmentMaps cleanly onto Bible Brain's ~3,349 Bibles across ~2,306 languages.

A budgeting tool developed for OBT that complements every other department with field employees: plans, spend, and reconciliation living in the same platform the field already uses, instead of a constellation of spreadsheets.

• OBT-first designBuilt around how Oral Bible Translation projects actually budget in the field.
• Every field departmentThe same model extends to LRD, GP, Travel, anywhere FCBH has people deployed.
• Finance Hub alignmentSits beside approvals, wire log, and reconciliation in the shell's Finance module.
• Specced end-to-endWill own budget build, multi-level approval routing, receipt intake with AI matching, reconciliation, and export to Finance Hub, landing in stages.

Glyph stays narrow on purpose. It does the two things FCBH actually needs a code for, does them cleanly, and keeps the data on our side of the wall.

• Scan to ScriptureA code on print media opens the right app, the right language, the right book. The shortest path from paper to a phone playing the Word.
• Scan to saveAt a donor event, a card hands over a contact in one tap, no typing, no lost business cards on the floor by Monday.
• Brand it onceFCBH color and mark drop into the code so it looks like ours, not a generic black-and-white grid.
• Built for the printerExport at the size and resolution the job needs, so a code reads the same on a badge and a backdrop.
• No middlemanStatic codes point straight at our own URLs. Nothing sits between the scan and the destination to count it or sell it.
• Lives in the shellSame Battlefield sign-on as everything else, reachable from the launcher, no separate account to make a code.

A dynamic forms platform: any team builds a form, publishes it, and collects responses, photos included, with video arriving at v1.5. Authors and respondents never share a surface, by design.

• Two planes, on purposeA locked control plane for form authors, a public plane for respondents, with org isolation enforced by row-level security.
• Uploads quarantinedEvery attachment lands in quarantine, gets sniffed by magic bytes, then promotes. Nothing unvetted reaches storage.
• Presigned deliveryFiles serve only through short-lived presigned links; the browser never touches the bucket.
• Photos now, video nextPhoto attachments in the MVP; video capture lands at v1.5.

Warehouse and equipment inventory: counting and tracking stock across the org. The surface is live today. Straight talk on the plumbing: phase 0 runs on a deterministic file store in the repo, and the database lands in a later phase.

• Count and trackStructured stock counts for warehouse and equipment, not another spreadsheet.
• One badge inAny authenticated Battlefield session carries the baseline warehouse-counter role.
• Multilingual from day oneLocalized from the first release, ready for wherever the shelves are.
• File store for nowThe data layer is a file store today, stated plainly; the database comes with the next phase.

Battlefield's unified, metered AI gateway. Phase 0 fronts Claude with Alfred's own key: a caller sends its Battlefield token and Alfred injects the provider key server-side, so no client ever holds one. Live today; the rest of the fleet adopts it in phase 1, and that adoption is gated. The Alfred voice surface on page 22 rides this same door: one product, spoken and wired.

• Deny by defaultEvery route starts closed, and the model catalog itself is gated.
• Metered, alwaysOne usage row per call, written even when the call fails. Spend is measured, never guessed.
• No keys in clientsCallers forward a bf_token; the provider key lives server-side with Alfred alone.
• Pluggable backendA local or governed engine drops in later with no route changes.

Beyond the shared floor, the services carrying the most sensitive traffic (messages, mail, meetings, Scripture in hostile regions) each add their own layers.

• Pulse · messagingEncrypted in transit (HTTPS with HSTS) and at rest (database under an FCBH-held KMS key, attachments encrypted in S3). Self-hosted video. Message-level end-to-end encryption is not implemented.
• Archangel · mailEncrypted local store (SQLCipher, keys in the OS keychain). S/MIME signing. AI sees metadata, never the body.
• Scribe · meetingsConsent-first capture: in-band, identity-bound, auto-purged. Sensitive meetings transcribe in-tenant, audio never leaves FCBH ground. v0 has no recording surface at all.
• Geauxjüre · the readerThree tiers for hostile regions: neutral app identity, proxy + rotating domains, PIN + biometric + wipe-after-N, panic-wipe. Offline gated by server-side grants.
• Vault · documents & e-signSigned documents deposit server-to-server into FCBH-owned storage. Single sign-on, full audit of who signed what, no consumer cloud.
• On the hardening listScheduled and stated honestly: message encryption, device PIN lock, AI → in-house Bedrock, retention + audit logging.

FCBH's workforce is global and multilingual, so the interface can't assume fluent English or perfect eyesight. Access is a design requirement, not a checkbox.

• Icon-drivenEvery key action is completable through icons, usable by staff across the ~2,306 languages FCBH serves, without fluent English.
• Never color aloneStatus reads as icon + color + label together, legible for color-blind users and in grayscale on a printed page.
• Keyboard-firstThe shell and Archangel drive entirely from the keyboard with a command palette, no mouse required.
• Readable by defaultGenerous type, strong contrast, and semantic structure so screen readers and tired eyes both keep up.
• Voice accessAlfred adds hands-free, spoken navigation and briefings, for accessibility and hands-busy field work alike.
• Built toward WCAG AADesigned to the principles auditors check; accessibility is a review gate on every page, not an afterthought.