Skip to content

Under active development

Development status →
TACITUS
Section pages

Context collection / staged product direction

Useful expertise.
Its scope comes with it.

Start by preserving the method behind your own repeated briefs. The proposed offering is curated, maintained evidence-linked context with declared scope, source rights and review state. Pricing and purchase are unavailable.

Local illustrative listings and buyer-review artifacts work here. Seller publishing, payments, identities, hosted sharing and independently verified credentials are not implemented.

Source-backed learning collection / editorial drafts

Explore the evidence.
Carry the context forward.

Inspect a policy question, its sources and its unresolved judgments. Try a cited context export, then create a draft of your own.

Browser-created editorial downloads use tacitus-editorial-draft/1, a readable JSON teaching format. PRAXIS attachment, seller publishing and payments are separate capabilities. No purchase or hosted upload takes place here.

Preparation time is not the date a statement became true or a guarantee of source freshness. Inspect each source publication date and each claim’s scope.

The earlier v1 downloads are withdrawn: they required a world-validity start these sources do not establish. Preparation and publication dates cannot substitute for that missing fact. Corrected native-v2 research packages preserve unknown validity and are not compatible with the native-v1 catalog or extractive brief compiler. They remain unreviewed educational material, with no verified PRAXIS integration or general reuse license.

Read the corrected package verification receipts. These receipts concern packaging and preserved metadata, not expert conclusions. An embedded earlier pending-review checkpoint is historical; the external receipt describes the final package checks.

3 of 3 editorial capsules

AI governance and energy infrastructure

AI compute infrastructure: planning under demand uncertainty

A decision capsule for evaluating data-center proposals without confusing annual energy forecasts, peak capacity and local infrastructure obligations.

Prepared 2026-10-18T04:56:00Z · 2 sources

Humanitarian diplomacy and policy analysis

Humanitarian access: separate legal framework from operational feasibility

A decision capsule for structuring an access discussion while preserving uncertainty, civilian protection and the distinction between public law explanations and actual permissions.

Prepared 2026-10-18T04:56:00Z · 2 sources

Urban resilience and public health policy

NYC heat resilience: reaching risk beyond emergency days

A decision capsule for comparing affordable home cooling, accessible cooling spaces and neighborhood outreach before the next warm season.

Prepared 2026-10-18T04:56:00Z · 2 sources

AI compute infrastructure: planning under demand uncertainty

compute-infrastructure-governance · Prepared 2026-10-18T04:56:00Z · Human review required · Revision recorded 2026-10-18T05:35:00Z

fact · us-historical-demand

The LBNL report estimates U.S. data centers used 192 TWh in 2024, or 4.7% of U.S. electricity.

Provenance: attributed source summary

Qualification: A modeled historical estimate for all data centers within the report’s scope, not AI workloads alone. Cryptocurrency mining is excluded.

World-validity is not established by preparation or publication dates.

Inspect temporal scope
{
  "publisherDates": {
    "lbnl": "2026-06-18"
  },
  "recordedAt": "2026-10-18T05:35:00Z",
  "observationPeriod": {
    "year": 2024
  },
  "forecastHorizon": null,
  "worldValidity": {
    "status": "unknown",
    "from": null,
    "until": null
  }
}

Sources: lbnl

fact · us-forecast-demand

The LBNL 2030 reference projection is 649 TWh; a compounded sensitivity stress-test range spans 521–843 TWh.

Provenance: attributed source summary

Qualification: Projection assumptions use late-2025 information. The stress-test range is not a probabilistic confidence interval and does not capture every structural discontinuity; it is neither observed demand nor committed project load.

World-validity is not established by preparation or publication dates.

Inspect temporal scope
{
  "publisherDates": {
    "lbnl": "2026-06-18"
  },
  "recordedAt": "2026-10-18T05:35:00Z",
  "observationPeriod": null,
  "forecastHorizon": {
    "year": 2030
  },
  "worldValidity": {
    "status": "unknown",
    "from": null,
    "until": null
  }
}

Sources: lbnl

fact · global-demand

The IEA’s 2026 executive summary projects global data-center electricity use rising from 485 TWh in 2025 to about 950 TWh in 2030.

Provenance: attributed source summary

Qualification: A global projection; it cannot be substituted for a U.S. forecast or a local grid impact study. It concerns all data centers, not exclusively AI workloads. IEA and LBNL models are not one harmonized dataset.

World-validity is not established by preparation or publication dates.

Inspect temporal scope
{
  "publisherDates": {
    "iea": "2026"
  },
  "recordedAt": "2026-10-18T05:35:00Z",
  "observationPeriod": {
    "baselineYear": 2025,
    "status": "publisher estimate"
  },
  "forecastHorizon": {
    "year": 2030
  },
  "worldValidity": {
    "status": "unknown",
    "from": null,
    "until": null
  }
}

Sources: iea

analysis · capacity-distinction

Annual TWh cannot by itself determine a proposed facility’s peak MW demand, interconnection cost or reliability impact. Local load shape and engineering evidence are necessary.

Provenance: analyst proposal

Assumptions: General evidence may not transfer to a specific decision without local inputs

Analytical dependencies: us-historical-demand, us-forecast-demand, global-demand. These do not establish native invalidation propagation.

Qualification: Analytical distinction; no site-specific engineering determination is made.

World-validity is not established by preparation or publication dates.

Inspect temporal scope
{
  "publisherDates": {
    "lbnl": "2026-06-18",
    "iea": "2026"
  },
  "recordedAt": "2026-10-18T05:35:00Z",
  "observationPeriod": null,
  "forecastHorizon": null,
  "worldValidity": {
    "status": "unknown",
    "from": null,
    "until": null
  }
}

Sources: lbnl, iea

scenario · compute-scenario

A public planning body is considering a phased data-center project and must decide what evidence to require before infrastructure commitments.

Provenance: illustrative scenario · illustrative scenario, not an actual event

Assumptions: Illustrative context only; no actual event asserted

Qualification: Illustrative governance scenario, not an identified project or an existing permitting decision.

World-validity is not established by preparation or publication dates.

Inspect temporal scope
{
  "publisherDates": {},
  "recordedAt": "2026-10-18T05:35:00Z",
  "observationPeriod": null,
  "forecastHorizon": null,
  "worldValidity": {
    "status": "unknown",
    "from": null,
    "until": null
  }
}

Sources: No source citation; analyst-generated material

Sources and provenance
Open questions, limitations and rights

Questions

  • What must a developer demonstrate before each capacity tranche is approved, and which assumptions would make staging ineffective?
  • What is committed load versus speculative expansion, and who bears costs if demand does not arrive?
  • Which flexibility claims are contractually enforceable and technically demonstrated?
  • What local grid, water, land-use and community constraints remain unmeasured?

Limitations

  • Educational research draft; no independent subject-matter review.
  • Source-linked paraphrases are not authenticated publisher excerpts.
  • No live operational feed or private data. No model output is treated as independent external evidence; recommendations remain analytical proposals.
  • Graph edges and options are analytical proposals unless explicitly sourced.
  • No local engineering, water-use, tariff or project-finance data is included.
  • National and global projections have different scope; do not add them together.
  • Native assertion dependencies are empty; analytical dependency edges below do not establish native invalidation propagation.
  • A digest can be recomputed by an editor; it is not a trusted signature or source authentication.
  • Native archive structural validation does not establish source truth, expert review or live PRAXIS compatibility. This revision requires explicit native-v2 adaptation; it is not a v1 exchange.

Original assistant-authored TACITUS paraphrases and analysis; no publisher text, images or datasets bundled. Display and delivery are user-authorized; general reuse terms for original TACITUS material are not specified. Linked source licenses apply only to their respective materials. Hashes identify summary bytes, not publisher identity, endorsement, truth or ongoing rights.

Download native-v2 research package

Create your own local editorial draft

Start with a question and one source. Your form stays in this page until you download it or leave. Source URLs are recorded, not fetched or verified. Avoid sensitive material on a shared device.

Small demonstration collection / manually authored

Find the distinction
your next task needs.

Inspect applicability, provenance, rights and maintenance before adopting a method. These are illustrative packs, not a live marketplace or independently verified expert credentials.

Filter applicability date, author and reviewer

4 of 4 illustrative packs.

Policy analysis / en

Legislative stage check

Review a policy brief. A sentence turns a proposed start or a request into an adopted obligation.

legislative-stage@r1 · Illustrative / local review required

Conflict analysis / en

Contextual terminology check

Edit an armed-group description. An alias, a component and an organization are treated as the same identity, or one designation becomes a global label.

contextual-terminology@r1 · Illustrative / local review required

Narrative analysis / en

Repeated reporting check

Update a narrative assessment. Several publications repeat a claim and the brief calls them independent corroboration.

source-independence@r1 · Illustrative / local review required

Statecraft / en

Conditional commitment review

Prepare a negotiation handover. A participant says “we are agreed” without evidence of the other party’s acceptance.

commitment-scope@r1 · Illustrative / local review required

Selected pack / legislative-stage@r1

Legislative stage check

Expected output: The revised consultation considers July 2027; adoption has not been confirmed.

Scope, worked example and method
Decision cue
A sentence turns a proposed start or a request into an adopted obligation.
Question to ask
Who can decide, on which text, at which stage, and what evidence would justify stronger wording?
Applicable setting
The synthetic January/July assignment. Historical EU material illustrates a distinct named procedure.
Excluded setting
Legal advice, automatic deadline calculation, other jurisdictions without a specialist, and live compliance assurance.
Required evidence
  • S01 §1: proposal and non-adoption
  • S02 §2: industry request
  • S03 §1 when available: revised option
  • S04 §1–3: mandate and reviewer correction
Acceptable example
The revised consultation considers July 2027; adoption has not been confirmed.
Counterexample
July 2027 is the adopted start and the pilot is mandatory.
Competing interpretation / uncertainty
Adoption and funding remain unresolved. A later proposal does not erase an earlier proposal.
Escalation
Missing instrument, disputed authority, ambiguous provision or consequential legal interpretation.
Output constraint
Retain proposal modality, request status, optional pilot and unresolved funding in the sentence.
Author / review assertion
TACITUS website author (illustrative role). Authored teaching review; no independent specialist review. Scope: teaching method and sample wording; reservations: Adoption and funding remain unresolved. A later proposal does not erase an earlier proposal.

legislative-stage@r1 · reviewed 2026-10-03 · Illustrative / local review required

Lineage, sources, rights and maintenance
Included / omitted
Scoped method, examples, author assertions and reference links. No licensed publisher corpus, client documents or independent credential verification.
Revision / lineage
r1; original authored listing, no parent or seller fork. Local copies create explicit lineage.
Applicability / last review / refresh
2026-10-01–2026-10-31 / 2026-10-03 / New consultation or adoption instrument; changed mandate, provision or jurisdiction.
Source coverage / failure conditions
S01 §1: proposal and non-adoption; S02 §2: industry request; S03 §1 when available: revised option; S04 §1–3: mandate and reviewer correction. Missing instrument, disputed authority, ambiguous provision or consequential legal interpretation.
Rights / handling
Demo metadata only; no license grant. Source rights are separate. Redistribution and derivative-output rights require confirmation. Publicly available sources are not automatically redistributable.
Permitted uses / users / derivatives
Not established by the demo. Buyer must confirm recipients, permitted task, output reuse and redistribution with the rights holder.
Maintenance / update / withdrawal
No subscription, update entitlement or support commitment. A withdrawn hosted listing cannot recall exported copies. Pinned tasks remain unchanged until local adoption review.
Support / affiliations / conflicts
No paid support route or withdrawal contract. No outside expert, affiliation, partnership or independently verified credential is asserted.
Technical format
tacitus-web-context/1 website view model. Production schema 3 and older capsule/v2 compatibility remain separate; no new production standard.
Preview task context

What changed, and what can the steering group safely say?

Selected method: legislative-stage@r1. Inputs: S01 §1: proposal and non-adoption · S02 §2: industry request · S03 §1 when available: revised option · S04 §1–3: mandate and reviewer correction. Omitted: Legal advice, automatic deadline calculation, other jurisdictions without a specialist, and live compliance assurance.

Only the reporting-rule method has a complete saved briefing replay; terminology has its own local exercise. Other packs are inspectable guidance.

Add to demo task

An author cannot relicense a publisher’s corpus or a former client’s evidence through a capsule. Listing metadata does not enforce access or promise recall of downloaded copies.

Ask about an incident.
Review the method it suggests.

Worked incident → targeted questions → draft method → counterexample → human review → scoped artifact → another case → maintenance. This prefilled interview and analyst are fictional; public references inform the practice without endorsing TACITUS.

Open the local expert-interview example

Structured method draft / unapproved until local review

demo_schema
tacitus-method-interview/1
author
Fictional demonstration analyst
reviewer
Local visitor / self-asserted
task
A fictional analyst briefs a steering group about reporting-rule preparation by Day 16.
cue
The word adopted appears where the source only proposes a start.
requiredEvidence
E01 and S01 §1; ask for the authority and adoption instrument.
alternative
A later proposal could change preparation options. An adopted instrument would justify stronger language.
exclusions
Another jurisdiction, an ambiguous provision or a real legal obligation needs a specialist.
exampleAndCounterexample
Reject: July is adopted. Accept: July is considered; adoption unconfirmed.
rightsQuestions
Synthetic interview only. Source documents, translations and client-owned material need separate permission.
unarticulated
Judgment about political feasibility, negotiation and consequential decisions is not captured by this phrase check.
reviewScope
Articulated teaching answers only; no verified expert identity or factual certification.
Test the authored legislative method on the next task →

Edited interview answers are an inspectable artifact. They do not replace the authored replay method or create a compatible automated rule. Maintain definitions, reviewer reservations, revision history and refresh triggers before wider use.

Read the research on articulated practice and tacit knowing →

Test the collection in three stages.

1 / Private reuse

Preserve a team’s method and test a second brief. Include elicitation, setup, reviewer and maintenance effort.

2 / Controlled handover

Confirm recipients, semantic fidelity and source permissions. Imported author approval is provenance; each receiving task needs local review.

3 / Curated expert packs

A small manually reviewed collection should test author effort, buyer fit, maintenance and willingness to pay before marketplace machinery.

A capsule seal or hash is an identifier, not proof of authorship, factual accuracy, permissions or signature validity. Signing remains a roadmap item.

Search and terminologyMachine-readable index