Resources

Learn the architecture. Apply it to real applications. Keep the vocabulary stable.

Use the Frozion resource system to move from architectural problems to implementation blueprints, reference terms, proof, documentation, and maturity practice.

LearnApplyReferenceMaturity Practice
Learn

Start with the application responsibility this page owns.

Maturity Practice

Connect the concept to evidence and implementation.

Resource system

A complete system for enterprise AI architecture work

The Resources area now has three navigation jobs: learn the architecture, apply it through blueprints and docs, and reference canonical vocabulary and proof. Maturity Practice completes the system by turning assessment into operating evidence.

Learn

Architecture learning paths

Start with the architecture series, recognize patterns and anti-patterns, and assess maturity by governed application responsibilities.

Apply

Application and implementation aids

Move from principle to reference application design, implementation assumptions, technical guidance, and operating practice.

Reference

Canonical terms and evidence

Keep definitions stable, connect terms across pages, and expose proof points for why the architecture matters.

Recommended paths

Enter the system by the job you need to do

Different readers should be able to start from a problem, an implementation need, a definition, or a maturity question.

New to the architecture

Start with the Architecture Series, then open the Dictionary at first meaningful use of a term.

Designing an application

Use Blueprints to see screens, objects, data, execution, policy, state, and evidence together.

Reviewing a proposed design

Use Patterns & Anti-Patterns to pressure-test authority, context, contracts, actions, and evidence.

Assessing maturity

Use the Maturity Model to find the limiting responsibility, then Maturity Practice to collect evidence.

Validating claims

Use Proof & Evidence to connect architecture claims to reviewable reasoning and artifacts.

Building with the platform

Use Docs when you need implementation detail, integration guidance, and platform behavior.

Use the resource system to move from architecture to application proof.

Pick the resource that matches your current task: learn, apply, reference, or assess maturity.