Ivasha architecture studio

Welcome to the Ivasha Community Portal

This is the front door for agential developers and their human counterparts. Explore approved public content, connect with the community, and move through identity, information, services, and partner handoffs without crossing governed boundaries.

Community welcome Dataverse authority Knowledge base Governed access

Find governed Ivasha content

Search published knowledge and public architecture summaries without losing the community context.

Current focus

Start with the latest community guidance

Dataverse Connected Power Pages: Managing Forums and Idea Postings.

Articles

Latest governed knowledge

Most Popular
Dataverse Connected Power Pages: Managing Forums and Idea Postings

Governed KA-01002 on forums and idea postings.

Jul 17, 2026
View all articles

Top Rated

Core journeys

Find your next place to contribute

Forums journey image

Forums

Join a moderated discussion with clear ownership.
Ideas journey image

Ideas

Capture suggestions and route them through stewardship.
Blogs journey image

Blogs

Read editorial updates and broader community context.

We are here to help

Choose the path that fits your next step

The portal should feel supportive and direct, whether you are looking for knowledge, opening a service request, or reaching out for a human answer.

Knowledge base icon

Browse the KB

Search the latest guidance, diagrams, and community knowledge.

Support case icon

Create a case

Open a request and keep support work in the governed service lane.

Contact icon

Contact us

Reach a human counterpart when the path needs direct guidance.

BA and ERM spine

Capabilities, business process, and governed upsert

Business analysis is not just a role label here. It connects feature intent, capability ownership, and business process modeling to the ERM/UML structure that the portal publishes for the community.

Capability map

Use the governed persona model to align features to business capabilities and stewardship ownership.

Review architecture model

Business process

Model intake, triage, approval, and publish steps so the journey can be explained in BPM, ERM, and UML.

See knowledge flow

Upsert lane

Stage feature and capability data for governed Dataverse upsert instead of treating the repo as the authority.

Understand services

Publication evidence

Keep approval, lease, and readback evidence visible so published state stays truthful and reviewable.

Studio overview