.NET Framework Reference

Authoring rules follow the reference-writing guide (Korean-only, like the rest of doc/principal/). This document is that guide applied to this tree.

The two documents linked below are part of the framework doc tree, which stays Korean-only. Following those links lands on Korean content.

This document plays a different role from two existing documents.

• Guide 13. Interface catalog — introduces frequently used interfaces from a tutorial angle.
• .NET exact interface — the contract-owning document. It carries the full interface, signature for signature.
• This reference — collects only "what you need to know to complete this one call." It does not duplicate the contract text; it cites the exact interface instead.

Entry unit

One reference entry = one entry-point method. A method that produces an awaitable result ending in a terminal Async()/Async<TReply>()/Yield<TReply>() — RequestToChannel, SendToChannel, Publish — is an entry.

Modifiers such as .Timeout(...) or .Metadata(...) that the builder returned by that method exposes never become their own entry. They only appear inside that entry's "Options" table. A document that lists fluent-builder components method by method fails to answer what the caller actually needs — "what does this one call do" — and this rule exists to avoid that failure.

Category

The chapters use the same 8 categories as the public-contract audit categorization (contract-inventory). This taxonomy is already verified across languages, so this tree does not invent a new one.

Category	Status	Corresponding spec
Host lifecycle	Complete	06-framework-api, 30-host-relocation-flow
Topology discovery	Complete	07-channel-topology, 09-client-server-channel, 10-network-listener-identity, 21-location-runtime
Messaging execution	Complete	04-message-model, 05-async-execution-policy, 08-channel-messaging
Spot instance	Complete	12-spot-messaging, 15-spot-actor, 16-spot-address-messaging, 17-stage-wrapper-on-spot
Actor relocation	Complete	14-actor-model, 15-spot-actor, 20-session-actor-dispatch, 30-host-relocation-flow
Stream session	Complete	19-stream-session, 20-session-actor-dispatch
Location authority	Complete	21-location-runtime, 22-location-store-redis, 23-relocation-store-redis, 30-host-relocation-flow
Observability diagnostics	Complete	24-runtime-monitoring, 25-runtime-metrics, 26-message-flow-tracing, 27-flow-correlation, 29-transport-liveness

Numbering follows this same order (the same order contract-inventory uses for its categories).

ko and en are both complete, and the same structure has been extended to the remaining four framework languages (C++, Java, Kotlin, Node.js). This document tree is wired into mkdocs.yml nav.