Renderingla

Examples

Real Faber packages — not toy snippets. Source lives in the public faberlang/examples repository. Use these when you need to see how applications are structured, how CLIs are wired, or how the language corpus is organized.

How to run an example

# CLI on PATH (see Install)
faber --version

# Clone examples (and often norma as a sibling for library home)
git clone https://github.com/faberlang/examples.git
git clone https://github.com/faberlang/norma.git

# Type-check a package
faber check examples/ai-workbench/packages/faber-ai

# Build / run / test when the package supports it
faber build examples/ai-workbench/packages/faber-ai -t rust
faber test examples/ai-workbench/packages/faber-ai

Exact entry commands vary by package — read each package README.md.

Application packages

PackageRoleStart here
AI WorkbenchMulti-command CLI for local model inventory, embeddings, and inference workflows; Python harness validationexamples/ai-workbench · site: AI Workbench
ViviLiteFaber-native local mailspace CLI (file-backed + optional SQLite lane) for agent coordination commandsexamples/vivilite
coreutilsLarger application campaign reimplementing common utilities with parity harnessesexamples/coreutils
gpu-workloadGPU / systems workload rungs and contractsexamples/gpu-workload
scripta / script-kernelScripting and kernel-facing demosexamples/scripta
automationAutomation sketch packagesexamples/automation
reader-localeLocale pack demos for keyword remappingexamples/reader-locale
cista-labPackage-store lab materialexamples/cista-lab

Language corpus

The corpus tree is the keyword and construct reference: one directory per construct, many small .fab programs. It is the source of truth for the generated Corpus pages on this site.

SurfaceURL
Source treeexamples/corpus
Generated docs/corpus/
Ecosystem noteLanguage corpus

Stdlib tours

Norma standard-library exempla live in the norma repo, not under examples/:

Suggested learning order

1. Install the CLI. 2. Skim Quick tour for language shape. 3. Open corpus pages for any keyword you do not recognize (Corpus hub). 4. Read AI Workbench or ViviLite end-to-end for application shape. 5. Use Syntax and Tooling as references while editing.

Agent path