How tegarthegreat/palugada works
PALUGADA is a self-hosted control plane for AI-run companies. The principal workflow is: an owner configures goals and roles, submits work, and receives consequential decisions in an inbox; the platform plans and budgets tasks, runs agents through a controlled runtime and capability broker, then records outcomes for reporting and organizational learning. The console exposes this workflow alongside documented features such as schedules, bundles, skills, memory, audit, and cost controls. Relationships come from README statements and shown imports/calls; unsampled subsystem wiring is not asserted.
Main entry points: inbox.ts Approval inbox · engine.ts Task engine · tasks.ts Task lifecycle · App.tsx Web console
Components 22
Owner console
- Web console
console/src/App.tsx - Decision inbox
console/src/pages/Decisions.tsx - Owner API
src/owner/api.ts
Company governance
- Company structure
src/governance/structure.ts - Goals
src/domain/goals.ts - Company settings
src/settings/store.ts - Schedules and triggers
src/scheduler/windows.ts
Work orchestration
- Background worker
src/worker.ts - Task engine
src/engine/engine.ts - Task lifecycle
src/engine/tasks.ts - Spend guard
src/governance/spend-guard.ts - Approval inbox
src/inbox/inbox.ts
Agent execution
- Capability broker
src/broker/broker.ts - Agent runtime
src/runtime/cli.ts - Model providers
src/llm/client.ts
Learning and oversight
- Tenant database
src/db/tenant.ts - Event log
src/audit/event-log.ts - Company memory
src/memory/store.ts - Skills and evals
src/skills/skills.ts - Reports and alerts
src/reporting/alerts.ts - Company bundles
src/bundles/bundle.ts
Other components
- Owner
Connections 28
- Owner → Web console: manages company
README.md - Web console → Owner API: calls API
- Web console → Decision inbox: presents decisions
console/src/App.tsx - Owner → Decision inbox: reviews requests
README.md - Owner API → Approval inbox: serves decisions
- Company structure → Goals: organizes work
- Owner → Goals: sets direction
README.md - Schedules and triggers → Background worker: wakes work
- Background worker → Task engine: runs tasks
src/worker.ts - Task engine → Task lifecycle: claims and transitions
src/engine/engine.ts - Task engine → Capability broker: invokes capabilities
src/engine/engine.ts - Task lifecycle → Spend guard: checks spend
src/engine/tasks.ts - Capability broker → Approval inbox: requests approval
src/broker/broker.ts - Owner → Approval inbox: approves actions
README.md - Agent runtime → Capability broker: requests tools
README.md - Agent runtime → Model providers: uses model
- Task engine → Tenant database: loads tenant context
src/engine/engine.ts - Task lifecycle → Event log: appends events
src/engine/tasks.ts - Approval inbox → Task lifecycle: transitions tasks
src/inbox/inbox.ts - Approval inbox → Tenant database: reads and writes
src/inbox/inbox.ts - Task engine → Company memory: builds run context
- Skills and evals → Approval inbox: submits candidates
src/skills/skills.ts - Background worker → Reports and alerts: runs oversight
src/worker.ts - Company structure → Company bundles: supports configuration bundles
- Owner → Company memory: searches company knowledge
README.md - Owner → Skills and evals: reviews skills
- Owner → Schedules and triggers: sets recurring work
README.md - Owner → Reports and alerts: views costs and status
README.md