№ 06 · SYSTEMREC / azwerks-obsidian-themes
candidate

azwerks obsidian themes

azwerks obsidian themes is a theme and snippet suite for structured writing and knowledge-work vaults. It improves long-session reading, state recognition, and metadata-heavy notes through Radium-aligned tokens; evidence is partial until specimen screenshots, taxonomy, and verification are complete.

Built on Radium tokens and semantic state colors.

  • Obsidian
  • CSS
  • visual-system
  • knowledge-work
Domaindesign-systemVersionmulti-theme suiteUpdated2026-07-02MaintainerazwerksProofpartial

Overview

01

What it is

azwerks obsidian themes is a theme and snippet suite for structured writing and knowledge-work vaults. It improves long-session reading, state recognition, and metadata-heavy notes through Radium-aligned tokens; evidence is partial until specimen screenshots, taxonomy, and verification are complete.

Canonical facts

Domain
design-system
Version
multi-theme suite
Updated
2026-07-02
Maintainer
azwerks
Proof
partial
  • Specimen screenshots are still being prepared; the suite spans multiple themes at different versions.

How the record thinks

02

Key decisions

01

Decision

Should the theme-suite record be public now?

ChosenPublish the converted record as a public candidate after explicit user approval.

The user approved publication of all four project records on 2026-07-02. The record remains conservative, evidence-limited, and caveated.

Alternatives considered

  • Keep draft — Rejected because the user explicitly approved publication.
  • Publish individual theme records — Rejected because taxonomy and specimens still need review.

Consequences accepted

  • The record appears in public work indexes, search, command data, sitemap, and metadata.
  • Theme taxonomy, specimens, assets, and verification remain open matters.
  • Proof posture remains limited.
Visibility
public
Approval
user message, 2026-07-02

Lineage

03

History

Operations

Intake

  1. Intake2026-07-01

    completed

    Project root scanned

    The authorized theme-suite root was scanned and summarized in a project intake dossier.

    Intent
    Gather evidence without publishing or exposing draft content.
    Action
    Read safe project files and recorded public-readiness concerns in the dossier.
    Result
    A non-public candidate dossier exists for review.

    No screenshot generation, theme validation, or contrast test was performed.

Record conversion

  1. Record conversion2026-07-01

    current

    Public candidate record approved

    Converted the intake dossier into a public candidate content record with caveats, evidence, decisions, relations, and open matters.

    Intent
    Publish a reviewable suite-level record without overstating proof.
    Action
    Updated the content record to `visibility: public` after explicit user approval.
    Result
    The record appears on public routes with limited proof posture and unresolved taxonomy, asset, and verification matters.

    Taxonomy, specimens, assets, and verification remain incomplete.

How do you know?

04

Evidence

03

azwerks obsidian themes intake dossier

reviewed

Dossier summarizing the Obsidian theme suite, snippets, design specs, public-safety concerns, caveats, and open questions.

File:
docs/project-intake/candidates/azwerks-obsidian-themes.project-intake-v1.0.md
State:
intake dossier
Record state:
published candidate

The dossier is intake evidence; publication approval is recorded separately.

project scan index entry

reviewed

Scan index lists the authorized root, public-readiness status, evidence confidence, suggested classification, and proof posture.

File:
docs/project-intake/azwerks-project-scan-index-v1.0.md
State:
source-cited

The scan index records intake posture; publication approval is recorded separately.

project intake scanner report

reviewed

Scanner report documents authorized roots, commands run, public-safety findings, and the intake-time publication boundary.

File:
docs/project-intake/azwerks-project-intake-scanner-report-v1.0.md
State:
source-cited

The report records intake behavior only; verification commands for the external project were not run.

Unresolved

05

Open matters

03

Matter ledger

Open matters stay visible and separate from decisions.

Publication follow-up

  1. needs-taxonomy-reviewmat-project-azwerks-obsidian-themes-taxonomy

    open

    Decide suite or theme-level taxonomy

    The intake dossier treats the root as one theme suite but notes multiple theme folders.

    Position
    Keep this as one draft suite record until the user approves a different structure.

    Individual theme records are deferred.

  2. needs-public-safe-assetsmat-project-azwerks-obsidian-themes-assets

    open

    Review or generate public-safe specimens

    No reviewed screenshots were available during intake.

    Position
    Use no theme specimens until the user approves screenshots or generated visual evidence.

    Demo files and visual specimens may require privacy and license review.

  3. needs-verification-commandsmat-project-azwerks-obsidian-themes-verification

    open

    Verify theme claims

    The intake pass did not run contrast or theme verification commands.

    Position
    Do not claim current contrast, plugin compatibility, or release readiness until verified.

    Verification must be authorized separately.

Links

06

Relations

Relations

How azwerks obsidian themes relates to the rest of the register.

Workspace context

  • relates toazwerks nvim

    Both records concern editor and knowledge-work surfaces and are published as limited-proof candidate records.

COLOPHON · № 06REC / azwerks-obsidian-themes
Created
Updated
Record ID
REC / azwerks-obsidian-themes
Version
multi-theme suite
State
candidate
Maintained by
azwerks
Derived from
Built on Radium tokens and semantic state colors.

LimitsSuite taxonomy and specimen screenshots are being finalized.