/architecture-knowledge

name: architecture-knowledge
description: "Explain US architecture professional-practice terms, phases, deliverables, roles, delivery methods, AIA contract families, CSI documentation systems, or NCS at a high level. Use for questions such as “what is a CD set?” or “what does 50% CDs mean?”; do not use for code/jurisdiction, outline-spec, agreement-scope, or work-plan work."
allowed-tools:
  - Read
  - Grep
  - WebSearch
  - WebFetch

architecture-knowledge

Before acting, read the [host contract](../../docs/host-harness-contract.md) and this component’s [declaration](host-contract.json) (`skill:architecture-knowledge`). Load only applicable modes from the [shared catalog](../../corpus/host-contracts.json); declarations do not grant access or permission. Use the actual host’s [delivery route](../../docs/host-adapters.md).

This is a native source-directory and explanation procedure with no registered operation IDs. Use the host's available source retrieval and reasoning capabilities. No Arch Studio executable, process capability, project creation or record mutation is required for this workflow. Follow the [completion contract](../../docs/completion-reporting.md); a source listing is not retrieval or verification.

Sources and evidence

Find relevant original links in [the source catalog](../../corpus/sources/catalog.json), filtered by geography and topic. For substantive claims, retrieve the applicable original or authorized supplied document and record its publisher, URL/file, section/page, version/date and task scope. A linked or reachable source is not proof of applicability. If access, edition or identity is unresolved, leave dependent conclusions unresolved; no local table or model-memory fallback. Keep task evidence in the authorized workspace, outside the plugin.

A request only to list sources uses catalog metadata and states that coverage is limited to matching registered entries. It needs no source-content retrieval, setup or approval. Shared and state sources retain their scope; missing LA coverage never substitutes NYC.

Professional-practice orientation

Use `professional-practice` and `architecture-knowledge` topics for AIA, CSI and NCS navigation. Search original publications for the user's term. Interpret ambiguous “CD” from context; ask a short clarification only when the distinction materially changes the answer. Explain the supported meaning concisely with source/version and distinguish project-defined terminology from a publisher's terminology. Do not derive scope, billability, acceptance or phase completion from a generic term.

Do not reproduce protected forms, clauses, tables or reconstructed standards. For contract selection or clause interpretation, give source orientation and identify the need for the governing agreement and qualified review; this skill does not choose a form or provide legal conclusions. Route actual agreement-scope work to agreement, specifications to spec-writer, planning to workplan and geographic code work to its appropriate owner. No project setup or record writes are needed for terminology.