ObservaStory

Public proof of concept

ObservaStory 1.0 beta

Explore the environment in a working example vault.

This beta demonstrates the current narrative-development engine, workspaces, and lenses. It is source-based, desktop-focused, and intentionally honest about its rough edges.

Open the beta source Read safety guidance first

Before you begin

Use the example project—or a disposable copy.

The beta can modify Markdown frontmatter and includes explicit content-management commands. Do not begin with your only copy of a manuscript. Keep a restorable backup, inspect changes, and never paste private story material into a support request.

What the beta demonstrates

A complete narrative-development loop, not a finished consumer installer.

The current distribution is a proof-of-concept Obsidian vault plus reusable tools. It is not yet listed in the Obsidian Community directory and does not have a finalized automatic update channel.

01

Compose & register

Keep loose writing unregistered, then mark durable scenes explicitly with type: scene.

02

Refresh observations

Queue locally configured evaluation against bounded scene and story context.

03

Explore ObservaStory

Use Storyboard, scene, chronology, voice, truth, goal, trajectory, and processing workspaces.

Manual beta setup

What you need to explore it.

These are the current proof-of-concept dependencies, not a promise about the eventual packaged product.

  1. 01

    Obsidian on desktop

    Use a desktop Obsidian vault. The current tools are not presented as mobile-compatible.

  2. 02

    Three Obsidian community plugins

    Install and enable Templater, Dataview, and Charts. Review each plugin’s permissions and documentation before using private material.

  3. 03

    Node.js 20 or newer

    Node runs the evaluation engine, queue, scheduler, indexing, and content-management commands.

  4. 04

    A locally configured model

    The proof of concept is designed around Ollama. Verify the configured endpoint and do not expose it to the public internet.

  5. 05

    The public POC and tools repositories

    Follow the repository README for the current source layout and configuration steps. The example vault is the safest first tour.

PRIMARY BETAObservaStory POC

Example vault, ObservaStory workspaces, command templates, and current product documentation.

 ENGINEobservastory-tools

Reusable evaluation, queue, chronology, truth, indexing, and content-management code.

A cautious first run

Prove the path before trusting the batch.

  1. 1. Open the example vault

    Learn the content boundary: story material, ObservaStory interface, command templates, and generated state.

  2. 2. Verify local configuration

    Confirm paths, the model endpoint, enabled evaluations, and the folders included in processing.

  3. 3. Run one registered scene

    Inspect the resulting ai.observations frontmatter and confirm the evidence and scope make sense.

  4. 4. Explore before expanding

    Open the Scene Development Map, Storyboard, Truth Ledger, and Processing Status before queuing a larger pass.

  5. 5. Bring your own copy later

    Only after the example behaves as expected should you test against a disposable copy of your own project.

Beta boundaries

Specific enough to be useful. Limited enough to be believable.

Area
Current beta
Not claimed
Installation
Manual, source-based setup documented in the POC.
Community-directory listing or automatic updates.
Execution
Desktop tools and a locally configured model.
Mobile support or hosted inference.
Collaboration
Author-owned files in a local Obsidian project.
Cloud sync or multi-user editing.
Stability
A working proof of concept for informed testers.
Production guarantees, data recovery, or professional fitness.