Technology Architects - IASA Global

Search Btabok

Search BTABoK for articles, canvases, competencies, and concepts by keyword or topic. Returns SUMMARIES from the unified BTABoK catalog. Use get_article, get_canvas, or get_content to fetch full content by documentId. IMPORTANT: Only present information explicitly contained in this response. Do not supplement, infer, or extrapolate beyond what is returned. If content is incomplete, say so.

Get Canvas

Retrieve a BTABoK canvas by ID or search by name. Returns the canvas description, usage guidance, tags, and image URL. Use the usage field to understand how the canvas should be applied. Search by name when you don't have the canvas ID. IMPORTANT: Only present information explicitly contained in this response. Do not supplement, infer, or extrapolate beyond what is returned. If content is incomplete, say so.

Get Canvas Sections

Retrieve the full CoDL structure for a BTABoK canvas. Returns all sections (with fields, bounds, cardinality) plus the CoDL document. Use the canvas documentId from search_btabok or get_canvas results. Alternatively search by name if you don't have the documentId. IMPORTANT: Only present information explicitly contained in this response. Do not supplement, infer, or extrapolate beyond what is returned.

Get Article

Retrieve the FULL content of a BTABoK article by its documentId. Returns the complete article body text, not just a summary. Use the documentId from search_btabok results (collectionType 'Article'). IMPORTANT: Only present information explicitly contained in this response. Do not supplement, infer, or extrapolate beyond what is returned. If content is incomplete, say so.

Get Content

Retrieve the FULL content of a BTABoK concept or competency by its documentId. Returns the complete description, levels, and tags — not just a summary. Use the documentId from search_btabok results. Specify the type: 'Concept' or 'Competency' (from the collectionType in search results). IMPORTANT: Only present information explicitly contained in this response. Do not supplement, infer, or extrapolate beyond what is returned. If content is incomplete, say so.

Check Completeness

Validate a filled-in architecture artifact against a JSON Schema. Pass a CoDL JSON Schema and the architect's work as JSON. The tool checks: 1) Required fields are present, 2) Fields have meaningful content (not empty), 3) Cross-references to other canvases are populated. Returns a structured assessment with gaps and recommendations. Note: CoDL schemas are not yet stored in the database. Provide the schema directly. IMPORTANT: Only present information explicitly contained in this response. Do no

Get Guidance For Role

Get BTABoK competency guidance for a specific architect role or specialization. Searches BTABoK competencies by role name and returns relevant competencies with their levels. Use get_content with documentId to fetch full competency descriptions. IMPORTANT: Only present information explicitly contained in this response. Do not supplement, infer, or extrapolate beyond what is returned. If content is incomplete, say so.

Search Patterns

Search BTABoK for architecture patterns applicable to a specific problem. Accepts the problem description plus optional code context and quality attributes to return patterns ranked by relevance with trade-off guidance. Returns: matched patterns with certainty, relevant competencies for trade-off analysis, and suggested BTABoK canvases (e.g. ADR) for documenting the decision. Use get_article to read a full pattern. Use get_canvas for any suggested canvas. IMPORTANT: Only present information expl

Loom Solutions

List, create, or diagnose Loom solution design spaces for the authenticated user. action=list (default): returns the solutions you own IN YOUR PERSONAL SPACE. It is NOT every solution you can reach: loom-service filters this list to orgId IS NULL, so solutions belonging to an organization are absent even though you may read and write them. A solution id you were given is still usable with every other loom tool — address it directly. action=create: creates a new solution. name is required.

Loom Boards

List, get or CREATE architecture boards for a Loom solution. Boards are ReactFlow canvas diagrams that contain imported BTABoK canvases and shapes. action=list: returns all boards in a solution (id, name, description — no flowState). action=get: returns a single board's metadata and the canvases placed on it (id, name, position). flowState (ReactFlow layout JSON) is never returned: it is visual layout state, not content — entity items live in section_data, read via loom_entities action=get or lo

Btabok Viewpoints

The BTABoK viewpoint library and its concern catalog — 16 viewpoints, 45 concerns. A CONCERN is the unit of architectural design work: a question, and the model type(s) that answer it. action=viewpoints: the 16 viewpoints with their concern counts. action=concerns: concerns in one viewpoint (viewpointCode), or all of them. action=concern: one concern in full — question, binding, parsed notations, card rails. action=where: WHICH CONCERN SHOULD I MODEL THIS UNDER — pass a notation code (UML-SM) or

Loom Documents

Create, read, update, or delete architecture documents in a Loom solution. Documents store Tiptap rich-text content — architecture decision records, notes, analysis. action=list: returns all documents in a solution (id, name, description — no content body). action=get: returns a single document including its full content string. action=create: creates a new document. name is required. content is a plain text or JSON string. action=update: updates name, description, and/or content of an existing

Loom Entity Types

Manage entity type schemas (definitions) in a Loom solution design space. Entity types define WHAT kinds of design artifacts exist — e.g. Persona, Capability, Requirement. action=list: returns all entity types for a solution (both global BTABoK types and custom ones). action=get: returns details of a specific entity type including its attributeSchema. action=create: defines a new entity type. typeKey must be unique lowercase_underscore. typeName is display name. action=delete: removes a solution

Loom Entities

Create, read, update, delete, or search entity instances in a Loom solution design space. Entities are specific design artifacts: a named Persona, a specific Capability, a Requirement, etc. action=list: all entities of a typeKey in a solution (id, name — no content). Use action=get for the content. action=search: search entities by name substring within a typeKey. action=get: returns a single entity. Its `sections` (rebuilt from section_data, the store native canvases write) are the canonical co

Loom Graph

The orientation call for a Loom solution: its knowledge graph. Returns nodeTypes (the canvas CoDL specs that act as the class layer), nodes (entities with ids, types and paths), and typed edges (item-level canvasRef cells plus entity links, including model-shape traceability). Read this FIRST, then resolve detail with loom_codl_entity / loom_definition.

Loom Codl Entity

One entity as CoDL JSON — the structured truth behind a canvas card. Sections carry typed values (numbers, enums, ISO dates), many-cardinality sections list items by itemKey, cross-canvas references appear as explicit $ref objects, and decision matrices / CALM models come back as structured JSON rather than strings.

Loom Links

The full semantic edge set of a solution: canvasRef cell edges and entity links with kinds, labels and properties. Use for impact analysis — 'what depends on this decision?', 'which requirements does this model shape carry?'.

Loom Model

The CALM architecture models an entity carries, with every shape and relationship listed by id — the read you MUST do before editing shapes, because a shape can only be moved, relabelled or deleted by its id. Each model reports its `notation` (freeform-calm or c4 — a c4 diagram may only use official C4 element types), a `basis` token to send back on write ops so a concurrent edit is refused rather than silently overwritten, and the decisions/requirements attached to each shape and connector.

Loom Definition

A canvas type's CoDL definition — the ontology layer, authored in metis by the professional body and read-only here. Returns sections, typed fields, enum values, ranges and cross-canvas ref affinities: what an entity's fields MEAN and what it is allowed to link to.

Loom Validate Change Set

Dry-run a change-set against the live canvas definitions: field types, enum membership, numeric ranges, cardinality, and reference legality. For shape ops it also replays the whole sequence against the CALM document, so it catches a relationship with a missing endpoint, a shape type that is not legal in the model's notation, a delete that would strand connectors or attached decisions, and a model that has moved since your `basis`. Side-effect free. ALWAYS call this and show the user the proposed

Loom Apply Change Set

Validate then ATOMICALLY apply a change-set to the solution. Writes go through the same services the canvas UI uses, so boards open in a browser update live, and every application is audited (who, via what, full payload). Returns created entity IDs, the number of cells written and a modelsWritten summary, or the validation diagnostics if the set was rejected — nothing is partially applied. All shape ops on one model collapse into a single cell write, and the prior CALM document is captured in th

User Profile

Read or update the authenticated user's Metis profile. action=whoami: returns the resolved Clerk/Appwrite identity and editable field list. action=get: returns the full UserProfile. action=update: accepts user-editable fields (displayName, organization, title, phoneNumber, location, bio, socialLinks). All updates are limited to the authenticated user's own profile.

Ceu Log

View or add Continuing Education Unit (CEU) records for the authenticated user. action=list: returns the user's CEU history with status. action=add: submits a new CEU entry (requires name, unitsClaimed, unitType, activityType). All records are owned by the authenticated user and require admin approval to reach 'Approved' status.

Article Submission

Submit or list Journal article drafts for the authenticated contributor. action=submit: creates a new Journal article draft (requires name). Content, tags, and shortDescription are optional. action=list: returns the user's article submissions. Only users with the Journal role in the Contributors team (or Administrators) may submit.