Playbooks
Define the approved method, required evidence, checks, exceptions and stop conditions.
TEMRIK / Company
The human-control layer for AI-operated workflows.
TEMRIK is building a control plane around playbooks, agents, tools, evidence, authority, human approval and audit so AI can assist with work without quietly inheriting business authority.
Starting with construction.
What TEMRIK is
Enterprise software for controlling the boundary between AI capability and business authority.
Models can generate content. Agents can use tools and move work. The harder operating problem is deciding what information they may use, which rules apply, what evidence is required, who has authority and what may actually be released.
TEMRIK is designed for that control problem. It gives organisations a structured layer around AI-operated workflows rather than treating the model itself as the source of policy, permission or accountability.
The control plane
Seven concepts define the TEMRIK product model.
Agents
Prepare, analyse and recommend inside bounded tasks rather than inheriting business authority.
Tools
Connect permitted systems and actions to explicit scopes and workflow rules.
Evidence
Keep source material visible alongside proposed decisions and actions.
Authority
Separate what technology can do from what the organisation permits it to release.
Human approval
Keep consequential decisions with authorised people where the workflow requires it.
Audit
Connect actor, evidence, approval, action and outcome so material work can be reconstructed.
Why construction first
Construction makes the authority problem visible.
Construction work combines changing information, commercial consequence, formal approvals, multiple organisations and evidence that must remain connected to decisions. That makes it a strong first market for controlled AI-operated workflows.
See TEMRIK for construction →Beyond construction
The control model is broader than one industry.
The same architecture applies wherever AI-supported work needs explicit evidence, permissions, approval and audit. Expansion is a product architecture direction, not a claim that every industry, jurisdiction or integration is already supported.
See how implementation works →Human authority
Capability does not create permission.
TEMRIK separates preparation and recommendation from consequential release. Where a workflow requires approval, an authorised person remains responsible for the decision. The model does not give itself business authority.
Official TEMRIK surfaces
Product, application, investor and public technical surfaces.
Public website
The primary public TEMRIK product and company surface.
Client application
The official TEMRIK client application and operator portal.
Investor presentation
The official TEMRIK investor presentation surface.
Public playbooks
The verified public repository for TEMRIK playbook examples.
No official LinkedIn company page, separate TEMRIK GitHub organisation, office network, investor roster, funding history or certification status is asserted here unless it is separately verified.
Company identity
TEMRIK is the product and trading name.
The current Privacy Policy and Terms identify Galilee Consulting (ABN 98 393 389 946) as trading as TEMRIK. Those legal documents remain the source for the current legal operator information.
Procurement and implementation
Trust is handled through evidence. Delivery is handled through a repeatable method.
The Trust Centre separates current controls from provider dependencies and roadmap items. The implementation system moves one bounded workflow through discovery, authority mapping, configuration, UAT, acceptance, activation and review.
Understand the company through the product