Explore this section
Loading TACITUS
Under active development · Explore the workspace, the evidence, and the industry cases.
Development status →Loading TACITUS
Applications / business & geopolitical risk
A development matters when it changes a dependency, an obligation, or an assumption. TACITUS is developing knowledge structures that connect external evidence to the questions a business needs to review.
Proposed application · illustrative records · no live risk feed or forecasting claim
Where the knowledge earns its place
Strategy, insurance, logistics, and public-affairs teams each need a different view of the same event. Preserve the shared evidence and make the business-specific assumptions explicit.
Which shipment, supplier, or inventory assumption is affected?
Dependency-linked change briefWhich condition changed, and what evidence supports a review?
Dated exposure reviewWhich scenario assumption needs revisiting before a decision?
Assumption and trigger registerIs this a proposal, an adopted rule, or an implementation notice?
Source-linked obligations mapExplore a worked example
Follow a source into an assessment. Add a later record and see what needs to change. These fictional cases show the reasoning a team needs to preserve.
Strategy · shipping · insurance · supply chains
News becomes commercially useful when it connects to a route, supplier, contract, or assumption that the business can review.
The assessment only uses records available in the selected view.
2 source records
Selected source · R1
“Component A is scheduled through Eastport. Current stock covers ten working days.”
Connects a named route to an internal inventory assumption.
An illustrative dependency map is not a forecast, live monitoring service, or investment recommendation.
Initial · Exposure change brief
Eastport restrictions may affect a component route. Verify the booked vessel before changing the supply plan.
Confirm the inventory assumption, shipment identity, and arrival estimate with their owners before acting.
Can each proposed review action be traced to a dependency and dated evidence?
A practical first evaluation
Choose a past decision and a small, approved source set. Compare the resulting brief with the team’s existing work before discussing operational use.
A decision question, dated public notices, a non-sensitive dependency example, and a reviewer.
Source support, stale assumptions, missing dependencies, and whether the proposed action follows from the record.
Feasibility, data handling, scope, evaluation criteria, price, timing, and support before the work starts.