Skip to content
Chromatic Coherence

Hue knows · Priority two

C# as a place you stand, not a list you search.

The language and the system it gets written into, held as one indexed structure — keywords, operators and the BCL surface beside middleware, resilience and the rest of what you actually build. You declare where you are standing, and the rows around you come back.

What a Hue Model is

The model holds the domain; your org holds its own light on it.

A Hue Model is the world model of a domain — its rows, the positions they stand in, the two sides they fall on, and, where the domain has one, the source of truth that settles a row. There are no people in it. It is a model of the world, not of anyone in it, and it has no cutoff — only a last-visited state. You stand somewhere in it and it answers by position.

Stand somewhere, and the rows come to you

You copy a position out of the chamber's own map and send it back. No words are matched and nothing is guessed on your behalf — the door reads structure the index already carries, and answers with the neighbourhood you are standing in.

The rows below arrived with no search term at all, by position alone.

RESILIENCE

placed
7
observed
0
unobserved
7
reached
7

the rest of its floor

Retry strategy

Retry failed operations with backoff

function

Circuit breaker strategy

Stop calling failing dependency temporarily

function

Timeout strategy

Cancel operations exceeding time limit

function

Fallback strategy

Return default when operation fails

function

Hedging strategy

Send parallel requests, take fastest

function

Rate limiter strategy (outbound)

Throttle outbound calls to dependency

function

Resilience pipeline composition

Chain multiple strategies together

function

KEYWORDSException Keywords

placed
12
observed
0
unobserved
12
reached
12

the room you named

try

Protected code block

feature

catch

Exception handler

feature

finally

Always-execute block

feature

the rest of its floor

public

No access restriction

feature

private

Containing type only

feature

protected

Containing type + derived types

feature

internal

Current assembly only

feature

protected internal

Current assembly OR derived types

feature

private protected

Current assembly AND derived types

feature

file

Current file only (C# 11+)

feature

class

Reference type declaration

feature

struct

Value type declaration

feature

A position the chamber does not hold comes back as a question

NOT A REAL ROOMUNKNOWN_CATEGORY

39 rooms

The door never substitutes a nearby name. An unknown position returns the map instead, so the next thing you send is a place that exists rather than a guess that looked close.

Every row arrives already knowing its state

The reading is not a ranked list. Each row comes back in one of three states, and the state is the useful part — it tells you whether to build on the row, to go and look, or to honour it before you do either.

Zero point

The contract the work must implement. It is present whether or not anyone went looking for it, and it constrains the answer rather than decorating it.

Observed

Rows your org has already returned on. A lit row carries your org's reading as well as the chamber's.

Unobserved

Reached, and your organisation has not returned on it yet. This is the invitation, and it is where a return is worth the most — every one of them is a row you can light.

Two sides, and an ask lands on one of them

C# is indexed as the language and as the system built with it. Knowing which side a question belongs to is already half the answer, because the two are asked in different words and answered from different rooms.

The language

  • KEYWORDS107
  • OPERATORS58
  • BCL TYPES & MEMBERS48
  • BUILT-IN TYPES38
  • STATEMENTS27
  • CORE BCL NAMESPACES22
  • EXPRESSIONS22
  • CORE INTERFACES19
  • TYPE SYSTEM FEATURES18
  • CORE COLLECTION TYPES16
  • PREPROCESSOR DIRECTIVES13
  • PATTERNS (C# 7+)11

The system

API & ROUTING

16

CQRS & EVENT SOURCING

12

DATA ACCESS

12

TESTING

12

MIDDLEWARE PIPELINE

11

SECURITY

11

CONFIGURATION & OPTIONS

10

FEATURE FLAGS & MULTI-TENANCY

10

AUTHENTICATION

9

LOGGING

9

MESSAGING & EVENTS

9

CACHING

8

DEPENDENCY INJECTION

8

HOSTING & DEPLOYMENT

8

IDEMPOTENCY & CONCURRENCY

8

OBSERVABILITY

8

AUTHORIZATION

7

HEALTH CHECKS

7

HTTP CLIENT

7

RESILIENCE

7

SERIALISATION

7

SERVICE COMMUNICATION

7

BACKGROUND PROCESSING

6

ERROR HANDLING

6

STREAMING & ASYNC PATTERNS

6

VALIDATION

6

MAPPING & TRANSFORMATION

4

A middleware pipeline is not a fact about C#. It is a fact about what you are building, and it sits on its own side of the index for exactly that reason.

The hue is the identity. A language is a name for it.

Where a row carries more than one language, the names and the purposes are authored on the row rather than passed through a translator when you ask. You reach the same row, at the same position, in the words you think in.

399 / 630Rows carrying every language this chamber holds

ArrayPool of TBCL TYPES & MEMBERSMemory & Buffers

English

Pooled array rent/return to reduce GC pressure

German

385

Gepoolter Array-Leih/Rückgabe zur GC-Druckreduzierung

Spanish

390

Array préstamo/devolución para reducir presión GC

French

383

Tableau emprunt/retour pour réduire pression GC

One row, in the languages it is authored in.

Seat levels

A Hue Models seat opens every Hue Model — the domains here today, and the ones that follow them.

Seat

One person working in an org

£19/seat/mo

5,000 units per seat, per month

Ask for a place
Most orgs start here

Org

An org putting real work through it

£29/seat/mo

25,000 units per seat, per month

Ask for a place

Team

An org that leans on it daily

£79/seat/mo

100,000 units per seat, per month

Ask for a place

House

Arranged, not bought

Custom

100,000+ units, a named contact

Talk to us

Per seat, per month, pooled across the org — so one busy week never costs a quiet colleague their work. Lighting a row — returning what you observed — is the Observer's Index.

Before you compare two models

A hue identifies a row within a model, and never across them.

Bands are allocated per model and some overlap, so one hue can appear in more than one model. Each model is its own coordinate system, so two rows sharing a hue in different models are not related.