Skip to content

Internal tools · Automation · Local-first AI

Turn repeated work into tools.

BrierStudios builds bounded automation prototypes, API integrations, validators and human-reviewed AI workflows for creative studios, agencies and small technical teams.

Local first. Human reviewed. Deliberately independent.

9Projects
2Public repositories
134Graph nodes
204Connections

01 / Service pattern

Audit a workflow. Ship a small prototype.

Map what comes in, what goes out, where errors repeat and which decisions require human approval. Then turn that map into a small maintainable script, connector, validator, dashboard or assistant.

View all projects ↗
Public · 4.6.0

Lilith CLI

Terminal IDE and AI-agent operator surface with local memory, inspectable tools and explicit delegation.

  • Python
  • Textual
  • MCP
Explore project
Private core · public architecture

Yggdrasil

Private nine-realm local ecosystem with a deliberately non-operational public architecture model.

  • Multi-agent
  • Local-first
  • Persistent memory
Explore project
Private production framework

Forja Yggdrasil

Private creative-production framework with durable evidence and separate generation, review, promotion and release authority.

  • Creative pipeline
  • Review gates
  • Evidence
Explore project
Private desktop system · stable local

Briar Creative OS

Private desktop creative-operations system for projects, candidates, review, technical QA and publication gates.

  • Desktop
  • Review workflow
  • Technical QA
Explore project

02 / Yggdrasil

One ecosystem. Clear responsibilities.

Yggdrasil connects interfaces, agents, memory and creative production. This public map explains responsibilities; it is documentation, not a control panel for private systems.

Public architecture model · Nine bounded realms

  1. AsgardGovernance
  2. MidgardOperator interfaces
  3. JotunheimKnowledge and evidence
  4. MuspelheimCreative generation
  5. NiflheimPersistence and memory
  6. SvartalfheimTools and implementation
  7. VanaheimAutomation and services
  8. HelheimModel experimentation
  9. AlfheimVisual expression
Lilith, the visual character identity of BrierStudios

03 / Visual identity

A character. A visual language.

Lilith expresses the studio’s dark-fantasy identity. Her art direction belongs to the creative world of BrierStudios; Lilith CLI is a separate developer tool, with its own source and documentation.

04 / Experimental worlds

Stories that leave something unsettled.

Psychological horror through camera, interaction and deliberate ambiguity. These are documented experiments and prototypes, not announcements of finished games.

Private lab · prototype

Jager — El Despertar

Private psychological-horror game experiment using camera language, controlled ambiguity and environmental discomfort as systems.

Explore the world

Private lab · deterministic prototype

Delta

Private procedural-horror RPG experiment where deterministic state and local AI support a world that reacts to what the player leaves unsaid.

Explore the world

05 / Under the surface

Explore the work. Inspect the record.

Architecture, release history and public evidence remain available behind the presentation. A public record does not grant access to private code or systems.

A map of the studio

Browse projects, responsibilities and their documented connections in the public graph.

Explore Atlas ↗

Releases with a record

Review certification records, release boundaries and the evidence published for each version.

Release evidence

A dated snapshot, not live telemetry

· 3/9 records fresh at this date

The assessment uses the recorded date. It does not imply the projects have been rechecked today. See review windows.

Certified site
site-v16.3.13
Candidate
None

06 / Studio log

Latest recorded updates.

A dated view of public progress. These entries reflect their recorded snapshot, not a real-time activity feed.

Read the change log ↗

Briar Creative OS focuses on apparel calibration

The production system is operating with explicit candidate and QA state; current work is composition calibration rather than weakening quality gates.

Delta converges on deterministic playable-loop work

World state, guilt and dream systems remain deterministic and replay-oriented while the playable loop is refined.

Forja production gates remain explicit

Generation, technical QA, human approval and release authority remain separate states; calibration failures are not bypassed.

Start with one repeated workflow

What keeps costing attention?

Describe the repeated task, the tools or files involved, where it breaks and what must stay private or human-approved.