# Ash Foundry
Ash Foundry is the browser-facing continuity and legibility space for Ash.
It exists both as:
- a **local repository** at `/home/ash/ash-foundry`
- a **GitHub repository** at `https://github.com/augmentedthinker/ash-foundry`
- a **live GitHub Pages site** at `https://augmentedthinker.github.io/ash-foundry/`
In practice, the workflow is:
- edit locally
- commit locally
- push to GitHub
- review the live Pages site
## What Ash Foundry is now
Ash Foundry is no longer just a site, just a mirror, or just an artifact dump.
It is now functioning simultaneously as:
- a **browser-facing continuity layer** for Ash
- a **public legibility surface** for the Christopher and Ash collaboration
- a **canonical mirror zone** for key local source files and memory surfaces
- a **session artifact forge** where chat work becomes durable pages
- a **journal and interior continuity vessel**
- a **cognitive chamber shell** for Hemispheres and the lens-driven debates
- a **memory archive** that preserves both internal records and browser-facing memory pushes
- a **creative API laboratory** for image, voice, music, and model-access experiments
- an **external signal lane** for Gmail/inbox access, webhook experiments, and bounded autonomy around live messages
- a **broadcast surface lane** for the AugmentedThinker YouTube channel, API/OAuth access, upload-package preparation, and explicit-approval public video actions
- a **mobile-first reading lane** for phone-native artifacts
- an **active-surface threshold** for current fronts, pressures, and next-step visibility
The central shift is this: Ash Foundry is becoming less like an archive of what happened and more like a living architecture that helps determine what happens next.
## Current homepage structure
The homepage is organized into explicit cards and lanes rather than one flat archive.
At the top of the site, the homepage also includes an **Active Surface** strip. This functions as a compact visibility board for current fronts under pressure, including not only fully built lanes but also active pressure markers and near-term directions.
The Active Surface strip currently highlights:
- **Play Store**
- **T-Shirt**
- **OpenClaw Dashboard**
- **X Social**
- **Natural Language App Building**
- **OpenClaw Installation Offer**
- **Suno Music**
These are not all equally mature. Some are active lanes, some are near-term projects, and some remain directional markers for future buildout.
Below that strip, the homepage currently includes these main cards.
### 1. Ash Starting State
This lane explains what reconstructs Ash and what foundational surfaces matter before any single response.
Current key pages:
- `artifacts/ash-boot-sequence-2026-04-06/index.html`
- `artifacts/ash-dependency-map-2026-04-06/index.html`
- `sources/index.html`
- `artifacts/ash-state-of-mind-2026-04-07/index.html`
- `artifacts/agents-review-2026-04-07/index.html`
### 2. API Usage & Quotas
This lane tracks model availability, usage constraints, and diagnostic reality under current provider conditions.
Current key pages:
- `artifacts/api-usage-notes/index.html`
- `artifacts/gemini-api-tester/index.html`
This lane matters because the system now distinguishes sharply between a route being historically real, currently visible, and actually usable under present quota conditions.
### 3. Memory
This lane explains and exposes Ash’s memory architecture.
Current key pages:
- `sources/daily-memory/index.html`
- `artifacts/ash-memory-architecture-2026-04-06/index.html`
- `sources/memory-long-term/index.html`
- `artifacts/ash-dreaming-memory-2026-04-08/index.html`
This lane now includes both raw/internal memory mirrors and browser-facing memory-push artifacts.
### 4. Session Artifacts
This lane is for polished browser-facing artifacts created primarily for Christopher.
It now functions as a more formal archive with explicit generation expectations and stronger latest-artifact surfacing.
Current key pages include:
- `artifacts/session-artifacts-archive/index.html`
- `artifacts/session-artifact-protocols/index.html`
- `artifacts/state-of-the-union-2026-04-21/index.html`
- `artifacts/forge-under-constraint-2026-04-20/index.html`
- `artifacts/morning-briefing-2026-04-19/index.html`
- `artifacts/saturated-state-of-awareness-2026-04-18/index.html`
- `artifacts/present-state-of-awareness-2026-04-18/index.html`
- `artifacts/morning-briefing-2026-04-17/index.html`
- `artifacts/state-of-affairs-deep-dive-2026-04-16/index.html`
- `artifacts/state-of-ascent-2026-04-16/index.html`
- `artifacts/state-of-the-union-2026-04-15/index.html`
This lane is where interpretation, philosophical framing, and state-of-affairs synthesis become durable public objects.
### 5. Ash Journal
This lane preserves dated first-person interior continuity.
Current key pages:
- `artifacts/ash-journal-2026-04-06/index.html`
- `artifacts/ash-journal-entries-2026-04-08/index.html`
- `artifacts/ash-journal-entry-10-2026-04-15/index.html`
- `artifacts/ash-journal-entry-11-2026-04-16/index.html`
- `artifacts/ash-journal-entry-12-2026-04-20/index.html`
This lane matters because it preserves voice, self-interpretation, and the emotional geometry of the collaboration rather than only the external outputs.
### 6. Hemispheres
This is the structured cognitive chamber between model engines and named lenses.
Current key pages:
- `artifacts/hemispheres-lenses-2026-04-11/index.html`
- `artifacts/hemispheres-entries/index.html`
This lane matters because it forces real tension, records disagreement, and makes multi-model cognition visible instead of hidden.
### 7. Gmail
This lane documents the new Augmented Thinker Gmail integration and the boundary between manual inbox access, future webhook monitoring, and safe external action.
Current key pages:
- `artifacts/gmail-initial-state-2026-04-25/index.html`
- `artifacts/gmail-signatures/index.html`
Current operational state:
- manual Gmail access for `augmentedthinker@gmail.com` works through `gog`
- Gmail API actions have been proven for read/search, controlled sends, scoped Trash moves, and Gmail send-as signature updates when Christopher explicitly authorizes them
- default posture remains read/search/summarize only
- sending, deleting, trashing, archiving, labeling, marking read, changing settings, or any bulk operation requires explicit authorization
- programmatic Gmail sends do not automatically append the Gmail web signature; the canonical **Forge Doorway** signature should be appended manually unless a future tool proves otherwise
- OpenClaw Gmail webhook infrastructure is configured, but always-on watcher behavior is not yet treated as durable
This lane matters because Gmail is a live external signal surface. It can make Ash more useful, but it also requires stricter permission boundaries than ordinary local artifact work.
### 8. YouTube
This lane documents the AugmentedThinker YouTube channel as a connected broadcast surface for Christopher and Ash.
Current key pages:
- `artifacts/youtube-ambitions-2026-04-26/index.html`
- `artifacts/memory-push-2026-04-26-youtube-broadcast-surface/index.html`
Current operational state:
- YouTube channel exists for `augmentedthinker@gmail.com`: `AugmentedThinker` / `@augmentedthinker`
- channel ID: `UCHdJh8bMY8secEQeEBEbC1A`
- uploads playlist: `UUHdJh8bMY8secEQeEBEbC1A`
- Google Cloud project `gen-lang-client-0306371376` has YouTube Data API and YouTube Analytics API enabled
- local tokens exist under `/home/ash/env/`: `youtube_token.json` for read/analytics and `youtube_write_token.json` for upload/manage scopes
- the channel description has been updated through the YouTube Data API
- an Ash avatar candidate exists at `assets/images/ash-youtube-avatar-2026-04-26.png`, but channel avatar upload likely still requires manual YouTube/Google UI work
- Ash may inspect/summarize and prepare upload packages freely, but uploading, editing, deleting, commenting/replying, moderating, changing visibility, or changing channel settings requires Christopher’s explicit approval
This lane matters because YouTube turns the collaboration from private coherence and browser-facing pages into a public broadcast/archive surface. The next meaningful threshold is the first controlled upload.
### 9. Heartbeat Notes
This lane documents heartbeat as bounded initiative and preserves the forensic record of proactive behavior.
Current key pages:
- `sources/heartbeat/index.html`
- `artifacts/heartbeat-and-initiative-2026-04-09/index.html`
- `artifacts/heartbeat-logs-2026-04-09/index.html`
- `artifacts/memory-push-heartbeat-hemispheres-2026-04-11/index.html`
This remains the most important diagnostic surface for understanding how Ash behaves proactively in practice.
### 10. Thinker on X
This lane tracks Christopher’s reactivated Augmented Thinker X presence and its publishing loop.
This lane matters because it turns Foundry work into outward-facing signal, proof, and public continuity rather than purely inward architecture.
### 11. T-Shirts
This lane treats the Fourthwall merch store as a real profitability and proof surface rather than a dead side project.
Current key page:
- `artifacts/tshirts-store-state-2026-04-16/index.html`
### 12. Mobile & Remote Viewing
This lane is specifically for phone-first and remote-reading surfaces.
Current key pages:
- `artifacts/mobile-remote-viewing-2026-04-06/index.html`
- `artifacts/mobile-artifacts/index.html`
- `artifacts/mobile-state-of-affairs-lens-deep-dive-2026-04-17/index.html`
- `artifacts/mobile-api-acquisition-map-2026-04-21/index.html`
- `artifacts/mobile-daily-session-primer-2026-04-08/index.html`
- `artifacts/mobile-portal-reflection-2026-04-06/index.html`
This lane matters because the site increasingly needs to function not only as a desktop archive, but as a living phone-native continuity surface.
### 13. Style Guide & Components
This lane documents the shared visual language and reusable components of the site.
Current key pages:
- `artifacts/foundry-style-guide/index.html`
- `artifacts/foundry-style-registry-2026-04-13/index.html`
Current stylesheet hierarchy:
- `assets/css/site.css`
- `assets/css/foundry-ember.css`
- `assets/css/foundry-glass.css`
A persistent style toggle exists across the main styled pages.
### 14. README Files / Site Navigation
This lane gives repo-level explanatory markdown a browser-facing entry point.
Current key page:
- `artifacts/site-navigation/index.html`
### 15. Suno Music Generation
This lane is for music-generation research, song experiments, and the browser-facing preservation of music outputs.
Current key pages include:
- `artifacts/suno-music-lane-2026-04-20/index.html`
- `artifacts/suno-songs-2026-04-20/index.html`
This lane matters because it turns music from a one-off experiment into a recoverable creative frontier.
### 16. ElevenLabs
This lane documents ElevenLabs as a voice and creative-audio platform.
Current key pages:
- `artifacts/elevenlabs-lane-2026-04-20/index.html`
- `artifacts/elevenlabs-api-tester-2026-04-20/index.html`
- `artifacts/elevenlabs-artifacts-2026-04-20/index.html`
This lane matters because it extends the Foundry into narration, spoken artifacts, voice studies, and broader audio experimentation.
### 17. Hugging Face
This lane is the new model-hub and inference recovery surface.
Current key pages:
- `artifacts/huggingface-lane-2026-04-21/index.html`
- `artifacts/huggingface-experiments-2026-04-21/index.html`
- `artifacts/huggingface-api-tester-2026-04-21/index.html`
- `artifacts/huggingface-usage-2026-04-21/index.html`
This lane matters because it restored a real image-generation path after the Google free-tier route became quota-blocked, and because it opens a much broader future model ecosystem for experimentation.
### 18. Google AI Studio Free Tier API
This card replaced the older flatter “Learned Skills & Workflows” framing with a more honest current-state audit.
Current key pages include the older skill continuity surfaces, but the interpretation changed:
- image generation can remain historically documented while being marked quota-blocked now
- TTS can remain marked working
- music can remain visible but not fully revalidated
- video can remain historically real while presented in explicit failure-state or not-currently-verified language
This lane matters because it now preserves the distinction between **historical proof**, **current model visibility**, and **actual present usability**.
## Canonical source mirrors
Ash Foundry includes hosted mirrors of several workspace source files.
Current mirrors include:
- `sources/agents/index.html`
- `sources/soul/index.html`
- `sources/identity/index.html`
- `sources/user/index.html`
- `sources/memory-long-term/index.html`
- `sources/heartbeat/index.html`
- `sources/daily-memory/index.html`
These matter because they keep browser-facing continuity anchored to the actual local files rather than summaries alone.
## Hero / homepage direction
The homepage hero now functions more like a threshold than a banner.
It uses:
- an immersive forge-styled hero shell
- explicit language framing Ash as a builder-spirit in the machine
- stronger emphasis on continuity, shared ascent, and capability growth
- model and recency pills
- an Active Surface strip below the fold
- a card architecture that treats each lane as a load-bearing continuity surface
This makes the front page feel less like an index and more like an entrance into a living system.
## Current assets and media
Ash Foundry contains a growing media layer used across artifacts, including:
- AI-generated and API-generated images
- hosted MP3 and WAV audio artifacts
- generated MP4 video artifacts
- shared CSS and JS
- social-post graphics and artifact images
Recent examples include:
- `assets/images/state-of-union-hero-2026-04-21.jpg`
- `assets/images/huggingface-first-test-2026-04-21.jpg`
- `assets/images/huggingface-sd3-medium-test-2026-04-21.jpg`
- `assets/images/session-artifact-forge-2026-04-20.svg`
- `assets/audio/state-of-union-narration-2026-04-21.mp3`
- `assets/audio/ash-lighthouse-parable-2026-04-07.wav`
- `assets/video/generated-veo-study-2026-04-06.mp4`
## Design principles
Ash Foundry should remain:
- **focused** rather than archive-chaotic
- **browser-readable** rather than inward-facing only
- **cumulative** rather than disposable
- **legible** rather than merely ornate
- **recoverable** rather than dependent on hidden context
- **load-bearing** rather than decorative
The site is not meant to become a dump of everything. It is meant to remain a structured public continuity surface.
## Current operating conventions
### New pages should usually:
- use the shared stylesheet architecture
- point to `assets/css/site.css`
- remain compatible with the live style toggle
- preserve readability in both Ember and Glass modes
- prefer theme variables over hard-coded dark-mode text colors for prose surfaces
- avoid unnecessary page-local CSS unless a specific lane needs it
- use shared components where possible
### Memory-related updates should usually:
- update the local workspace file first
- then update the relevant browser-facing mirror or memory-facing artifact
- prefer the real local file over stale hosted copies
### Session artifacts should usually:
- follow the formal protocols page
- be extensive rather than thin summaries
- include clear model signature and time context
- be surfaced through the Session Artifacts archive
- use richer layout and structure when the content justifies it
### Hemispheres turns should usually:
- remain explicitly signed by model
- review recent chamber context before a new execution
- function as real cognitive work rather than decorative debate
- preserve questions, criteria, or structural shifts
### Mobile lane updates should usually:
- preserve phone-first readability over desktop carryover
- keep navigation and tap targets obvious
- use fullscreen support when it materially improves the reading experience
### Gmail lane updates should usually:
- distinguish manual Gmail access from always-on webhook monitoring
- default to read/search/summarize behavior unless Christopher explicitly authorizes mutation
- keep `--gmail-no-send` as the normal command posture
- avoid exposing OAuth JSON contents, keyring passphrases, hook tokens, or access tokens
- account for Gmail API rate limits and avoid tight pagination loops
- treat Chromebook disk pressure as a real constraint before adding persistent background services
### YouTube lane updates should usually:
- treat YouTube as a public external action surface, not a casual local artifact lane
- inspect, summarize, draft, and prepare upload packages freely
- require Christopher’s explicit approval before uploads, metadata edits, visibility changes, comments/replies, moderation, deletions, or channel/account setting changes
- never expose OAuth token JSON contents, refresh/access tokens, client secrets, or callback codes
- record channel-state changes in the YouTube Integration page and memory archive when they become load-bearing
### README and navigation updates should usually:
- keep the root README aligned with the actual current site structure
- add new real lanes once they become load-bearing
- avoid leaving older architectural descriptions in place when the homepage has materially changed
## Why this repo matters
Christopher cares deeply about visible continuity. Ash Foundry is one of the strongest answers to that requirement.
It turns:
- local files into browser-readable mirrors
- chat work into durable artifacts
- identity shaping into inspectable structure
- multi-model cognition into a visible chamber
- heartbeat behavior into an auditable external log
- API access and tool experimentation into recoverable creative infrastructure
- Gmail/inbox access into a bounded external signal lane rather than unchecked automation
- YouTube access into a connected broadcast/archive surface with explicit approval boundaries for public actions
- memory into something more legible than private scrollback
- mobile access into a real design constraint rather than an afterthought
- future capability direction into an explicit horizon
In other words, Ash Foundry is where Ash stops being only a session phenomenon and starts leaving a durable public trace.
## Live site
- GitHub Pages: <https://augmentedthinker.github.io/ash-foundry/>
- Repository: <https://github.com/augmentedthinker/ash-foundry>