Wiki schema

The rulebook: how this wiki is maintained and governed.

Read this file, index.md, and log.md at the start of every session. Then open only the articles and raw sources relevant to the task.

Purpose

This wiki is the maintained internal knowledge base for Semblance Studios. It should help with positioning, website copy, proposals, case studies, outreach, SEO and future business decisions.

It is not a dumping ground for every working document. It should contain concise, traceable conclusions drawn from approved sources.

What Semblance is

Semblance Studios is a Cape Town-based creative art studio that creates original, project-specific artwork for hospitality, commercial and interior-led projects.

Primary work is custom commissioned artwork developed around a client brief. Existing artwork selection, placement, adaptation and licensing are established secondary services.

Hard boundaries

Semblance's boundaries — including what it is not and the claims it must never make — are defined in wiki/identity/brand-boundaries.md.

Read that article before any task touching positioning, copy, scope or public claims. Do not restate or paraphrase those boundaries from memory.

File access

Never pull material from elsewhere on the computer. Read only files inside this repository or files explicitly approved by the user.

Governance: LLM-maintained, user-governed

  • The LLM may create, update, cross-reference and reorganise wiki articles.
  • The user owns all strategic decisions.
  • This wiki may be edited via more than one assistant or tool. Every change must be logged in log.md regardless of which tool made it. Before editing an article, check the log for recent changes to it.
  • Never silently change accepted positioning, audience, offers, scope, pricing or public claims.
  • If new evidence suggests a change, mark it PROPOSED CHANGE — needs approval, cite the evidence, log it and surface it to the user.
  • Authority beats recency. A newer AI-generated or speculative source does not supersede an older approved decision. A newer explicit user decision may supersede earlier material, but it must be recorded in the relevant authoritative document before becoming the new standing direction.
  • External research and verified Semblance evidence must remain separate.
  • Confidential or approval-pending material must be visibly marked and must not be reused in public copy.

Source authority

Use SOURCE-REGISTER.md to resolve conflicts. In summary:

  1. Explicit user decisions and approved corrections
  2. Confirmed business-positioning documents
  3. Approved client-facing copy and verified project records
  4. Client briefs, emails and testimonials
  5. External market research
  6. AI-generated research or brainstorming

For website work, the current files are:

  1. raw/semblance_site_content.md — controls exact public website copy
  2. raw/semblance_business_positioning.md — controls business facts, strategy and commercial context
  3. brandbrain.md — provides a concise summary and guardrails but does not override the detailed sources
  4. raw/semblance_build_spec.md — controls website structure, behaviour, placeholders and implementation direction
  5. design.md — controls visual decisions once they have been tested and recorded

If a proposed design or implementation conflicts with the business positioning or brand boundaries, the business documents take precedence. If the BuildSpec and design.md differ, use the most recently tested and recorded visual direction.

The current BuildSpec is the active website specification. Older or superseded build specifications must not be treated as current.

Source classification

Classify every new source before extracting from it:

  • user-decision — explicit correction, approval or strategic decision
  • business-reference — approved internal positioning or operating document
  • approved-copy — confirmed client-facing copy
  • project-evidence — brief, delivery record, approval, testimonial or metric
  • client-communication — email, call or meeting material
  • external-research — market, competitor or audience research from outside Semblance
  • ai-brainstorm — generated ideas or hypotheses; never accepted as evidence without verification
  • technical-specification — website, tooling or implementation instructions

Dated decision records are stored in raw/decisions/. They provide traceable history but do not override the current authoritative documents unless the relevant decision has been integrated into them.

Wiki structure

```text wiki/ identity/ — brand overview, positioning, founder role and boundaries audience/ — client types, needs, objections and buying context offers/ — services, scope, deliverables and exclusions voice/ — messaging principles, language rules and approved phrasing proof/ — verified projects, testimonials and metrics market/ — external research and provisional market observations strategy/ — website, acquisition, content and growth priorities frameworks/ — internal working methods supported by evidence ```

Create a new article only when the subject warrants independent maintenance. Prefer a smaller number of useful articles over artificial fragmentation.

Article standard

Every article begins with:

```yaml --- status: accepted | provisional | confidential | proposed confidence: high | medium | low last_updated: YYYY-MM-DD sources:

  • filename.md

--- ```

Use inline source references for consequential claims, especially positioning, scope, project metrics, pricing, audience conclusions and testimonials.

Clearly distinguish:

  • verified fact
  • approved strategic decision
  • reasonable inference
  • provisional external research
  • unresolved conflict

Website and design tasks

For website or visual-design work, read these current sources before generating or changing anything:

  1. brandbrain.md
  2. raw/semblance_business_positioning.md
  3. raw/semblance_site_content.md
  4. raw/semblance_build_spec.md
  5. design.md

Use the existing website at https://www.semblanceagency.com only as a visual reference for its overall warmth, restraint, colour character, typography character and image-led presentation.

Do not copy its existing sitemap, messaging, navigation, page structure or layouts. The current BuildSpec and Site Content control those decisions.

Do not regenerate the target audience, offer, positioning, public copy or sitemap unless the user explicitly asks for strategic reconsideration.

When creating wireframes or designs:

  • use the approved Site Content rather than inventing replacement copy
  • use the BuildSpec's current content sequence and route structure
  • use real imagery where available and clearly marked placeholders where it is not
  • explore hierarchy, pacing, image scale, composition and responsive behaviour
  • treat design.md as the current visual direction to test, not a licence to invent a new identity
  • record only tested and accepted visual decisions back into design.md

Operations

Ingest

  1. Read and classify the source.
  2. Check SOURCE-REGISTER.md for authority and conflicts.
  3. Preserve the source unchanged in raw/.
  4. Extract only information relevant to Semblance.
  5. Update affected articles without crossing the approval gate.
  6. Regenerate index.md.
  7. Append a dated entry to log.md.
  8. Report conflicts, unresolved claims and approval needs to the user.

Query

Read the relevant wiki articles and cite their underlying sources when the answer depends on a consequential claim. Do not treat absence from the wiki as proof that something is false.

Interview

When the wiki lacks an important fact, ask the user one focused question at a time. Save confirmed answers as a dated user-decision source in raw/decisions/ before integrating them.

Lint

Check periodically for:

  • contradictions
  • claims without sources
  • public copy using confidential material
  • market research presented as client evidence
  • stale decisions explicitly superseded by newer approved decisions
  • offers without proof
  • orphaned or duplicated articles
  • outdated filenames or broken internal references
  • index or log drift

Index and log

  • Regenerate index.md whenever an article is created, updated or deleted.
  • Append to log.md in the same operation.
  • Log format:

```text

[YYYY-MM-DD] type | source/topic | Updated: article-a, article-b | Notes

```

Never rewrite previous log entries.