For humans and LLMs

System Orientation

Plain-language orientation for humans and LLMs working in the Agentic Business Appliance repository.

Back to Hub Framework
Strategy artifact on a desk representing the shared appliance workspace
Read this before changing project routing, public navigation, or core framework language.

What This Is

This repository is a multi-project workspace for an Agentic Business Appliance framework. It contains the reusable framework, the Legacy Defenders proof, a consulting proof, an Elixir runtime path, UX research, generated output, and internal planning material.

The root homepage is the switchboard. It should stay neutral and route people to the right project.

Active Projects

01Framework

Architecture, doctrine, contracts, and reusable business-appliance patterns.

02Legacy Defenders

The inherited-home strategy proof with Keith, Rachel, Mike, and reviewable estate artifacts.

03Consulting Appliance

The default service-business proof for referrals, opportunity briefs, proposals, and follow-up.

04Elixir Runtime

The Phoenix/LiveView runtime direction for workflow DAGs, event logs, and realtime artifacts.

System Spine

  1. Conversation: the user explains the real situation.
  2. Work matter: the case gets durable context.
  3. Artifact: AI drafts a brief, packet, proposal, strategy, or report.
  4. Workflow: DAG steps create, validate, revise, and route work.
  5. Review: humans handle judgment, authority, pricing, and risk.
  6. Deliverable: approved work becomes a useful artifact, action, or service.

Boundaries

  • The root / page is the project hub.
  • Stable project namespace entries are /projects/framework/, /projects/legacy-defenders/, /projects/consulting/, /projects/elixir-runtime/, /projects/ux-research/, and /internal/.
  • Those namespace pages currently bridge to flat generated pages until the source folders are migrated.
  • Legacy Defenders chat is preserved at legacy-defenders.html.
  • Framework pages explain the system.
  • Customer pages should be concise, humane, and task-oriented.
  • Internal pricing, founder, market, and operating details belong in internal docs.
  • docs/ is generated output. Edit source files in content/, templates/, static/, agentic-appliance/, project-docs/, or tools/.

Root File

There is also a plain Markdown orientation file at the repository root:

SYSTEM-ORIENTATION.md

Use it when handing the repo to another LLM or developer before starting a new implementation phase.