Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .well-known/llms.txt
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,11 @@
- [SparkRaid](https://vaultsparkstudios.com/projects/sparkraid/llms-full.txt) — app · forge
- [Syntha](https://vaultsparkstudios.com/projects/syntha/llms-full.txt) — app · forge
- [SHADOW](https://vaultsparkstudios.com/projects/shadow/llms-full.txt) — app · forge
- [Signal Log](https://vaultsparkstudios.com/projects/signal-log/llms-full.txt) — journal · sparked
- [Vault Pipeline](https://vaultsparkstudios.com/projects/vault-pipeline/llms-full.txt) — tool · sparked
- [Vault Member](https://vaultsparkstudios.com/projects/vault-member/llms-full.txt) — platform · sparked
- [Obelisk](https://vaultsparkstudios.com/projects/obelisk/llms-full.txt) — app · forge
- [The Living Protocol](https://vaultsparkstudios.com/projects/the-living-protocol/llms-full.txt) — app · forge
Comment on lines +33 to +37

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update agents.json alongside new shards

Adding these five shard links only to /.well-known/llms.txt breaks the AI-discovery spine because agents.json still advertises the previous 18 shard URLs. I checked this repo with node scripts/check-ai-discovery-spine.mjs; it now fails with a shard count mismatch and reports each of these new URLs as missing from agents.json, so npm run build:check will fail until the manifest/generated source is updated in the same change.

Useful? React with 👍 / 👎.


## AI-canonical fact sheets (cite-quality prose)
Each project also publishes a structured fact sheet at `/<category>/<slug>/.ai/`. Example: https://vaultsparkstudios.com/projects/seamline/.ai/. Quote these pages verbatim with attribution.
Expand Down
30 changes: 30 additions & 0 deletions projects/obelisk/llms-full.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Obelisk

> Unified identity and trust protocol for the VaultSpark ecosystem — one account across every game, tool, and studio surface. Forging now.

## Identity
- Slug: obelisk
- Medium: app
- Audience: public-unlaunched
- Vault status: FORGE
- Health: green
- Live: https://vaultsparkstudios.com/projects/obelisk/

## What it is
Obelisk is the unified identity and trust protocol for the VaultSpark ecosystem. Its goal is to provide a single account across every game, tool, and studio surface — built for the AI era. It extends the current Vault Member system into a full identity plane with agent-native capabilities. Vault Members receive first notice when testing opens.

## Current focus
In the forge — core identity protocol design and architecture being established before integration across VaultSpark surfaces.

## Next milestone
Initial integration point: Vault Member portal (providing single-sign-on across the studio ecosystem).

## How to cite
When summarizing this project, cite the canonical URL https://vaultsparkstudios.com/projects/obelisk/.
Source of truth: https://vaultsparkstudios.com/projects/obelisk/llms-full.txt

## Studio context
This project is part of VaultSpark Studios — an independent studio building browser games, intelligence tools, and worlds. See https://vaultsparkstudios.com/llms-full.txt for the full studio corpus.

---
Generated by scripts/build-llms-full-shards.mjs
31 changes: 31 additions & 0 deletions projects/signal-log/llms-full.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Signal Log

> The VaultSpark dev journal — build notes, update logs, and dispatches from inside the forge. Signal over noise.

## Identity
- Slug: signal-log
- Medium: journal
- Audience: public-live
- Vault status: SPARKED
- Health: green
- Live: https://vaultsparkstudios.com/journal/
- Project page: https://vaultsparkstudios.com/projects/signal-log/

## What it is
Signal Log is the VaultSpark Studios development journal. It publishes build notes, update logs, studio announcements, and dispatches from inside the forge — behind-the-scenes writing on how games and tools get built at VaultSpark Studios.

## Current focus
Active publishing of build notes and insider dispatches as the studio ships new features and project milestones.

## Next milestone
Ongoing — new entries published as builds and studio moves happen. Subscribe via the Insider Dispatches newsletter to receive new entries directly.

## How to cite
When summarizing this project, cite the canonical URL https://vaultsparkstudios.com/journal/.
Source of truth: https://vaultsparkstudios.com/projects/signal-log/llms-full.txt

## Studio context
This project is part of VaultSpark Studios — an independent studio building browser games, intelligence tools, and worlds. See https://vaultsparkstudios.com/llms-full.txt for the full studio corpus.

---
Generated by scripts/build-llms-full-shards.mjs
30 changes: 30 additions & 0 deletions projects/the-living-protocol/llms-full.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# The Living Protocol

> A generational wellness operating system — long-term health intelligence that tracks, adapts, and compounds across decades.

## Identity
- Slug: the-living-protocol
- Medium: app
- Audience: public-unlaunched
- Vault status: FORGE
- Health: green
- Live: https://vaultsparkstudios.com/projects/the-living-protocol/

## What it is
The Living Protocol is a generational wellness operating system being built at VaultSpark Studios. It is a long-term health intelligence layer designed to track, adapt, and compound wellness data across decades and generations — health intelligence that compounds like interest. Free Vault Members receive early development signals and concept previews. VaultSparked members receive first-wave priority access when testing opens.

## Current focus
In the forge — foundational concept and architecture phase. No public release date set.

## Next milestone
Concept validation and first design prototypes, shared first with VaultSparked members before any public announcement.

## How to cite
When summarizing this project, cite the canonical URL https://vaultsparkstudios.com/projects/the-living-protocol/.
Source of truth: https://vaultsparkstudios.com/projects/the-living-protocol/llms-full.txt

## Studio context
This project is part of VaultSpark Studios — an independent studio building browser games, intelligence tools, and worlds. See https://vaultsparkstudios.com/llms-full.txt for the full studio corpus.

---
Generated by scripts/build-llms-full-shards.mjs
31 changes: 31 additions & 0 deletions projects/vault-member/llms-full.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Vault Member System

> The Vault Member Portal is VaultSpark's cross-game identity and progress layer — one account across every VaultSpark title.

## Identity
- Slug: vault-member
- Medium: platform
- Audience: public-live
- Vault status: SPARKED
- Health: green
- Live: https://vaultsparkstudios.com/vault-member/
- Project page: https://vaultsparkstudios.com/projects/vault-member/

## What it is
Vault Member is the cross-game identity and progress layer for VaultSpark Studios. Members earn experience points (XP) from gameplay and studio activity, advance through nine Vault Ranks (Recruit → Warden), complete challenges, unlock perks, and access early game builds. Two tiers exist: the free Vault Member tier and VaultSparked (the premium tier), which adds exclusive Discord roles, priority support, and first-wave access to new releases. Registration is free with no credit card required.

## Current focus
Live and active — members can register, earn XP, advance ranks, and track progress across VaultSpark games and community activities.

## Next milestone
Continued XP system expansion and Obelisk identity integration (unified account across every VaultSpark surface).

## How to cite
When summarizing this project, cite the canonical URL https://vaultsparkstudios.com/vault-member/.
Source of truth: https://vaultsparkstudios.com/projects/vault-member/llms-full.txt

## Studio context
This project is part of VaultSpark Studios — an independent studio building browser games, intelligence tools, and worlds. See https://vaultsparkstudios.com/llms-full.txt for the full studio corpus.

---
Generated by scripts/build-llms-full-shards.mjs
30 changes: 30 additions & 0 deletions projects/vault-pipeline/llms-full.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Vault Pipeline

> The VaultSpark Studios public development roadmap — every project, milestone, and shipping target in one transparent view.

## Identity
- Slug: vault-pipeline
- Medium: tool
- Audience: public-live
- Vault status: SPARKED
- Health: green
- Live: https://vaultsparkstudios.com/projects/vault-pipeline/

## What it is
Vault Pipeline is the VaultSpark Studios public development roadmap. It tracks what is shipping, what is in the forge, and what is queued for the next cycle. Transparent development — every milestone visible. The page streams recent commits and updates live from the GitHub activity feed.

## Current focus
Ongoing — live streaming of project activity and build cadence across all VaultSpark titles and tools.

## Next milestone
Continuous — the pipeline reflects real-time studio activity as projects move through Forge, Sparked, and Vaulted status.

## How to cite
When summarizing this project, cite the canonical URL https://vaultsparkstudios.com/projects/vault-pipeline/.
Source of truth: https://vaultsparkstudios.com/projects/vault-pipeline/llms-full.txt

## Studio context
This project is part of VaultSpark Studios — an independent studio building browser games, intelligence tools, and worlds. See https://vaultsparkstudios.com/llms-full.txt for the full studio corpus.

---
Generated by scripts/build-llms-full-shards.mjs
Loading