daftari 1.11.0 → 1.12.0

package/templates/reviewer-vault/.daftari/tensions.md

@@ -0,0 +1,6 @@
+
+## 2026-05-12 — Managed connectors vs authored pipelines
+- **Source A:** competitive-intel/helios-connect-overview.md says managed connectors should be first-class control-plane objects so teams skip pipeline authoring entirely
+- **Source B:** competitive-intel/aurora-pipelines-positioning.md says ingestion belongs in an authored, reviewable artifact alongside the rest of the transformation graph
+- **Status:** unresolved
+- **Logged by:** agent:claude-code

package/templates/reviewer-vault/_drafts/moonshot-agentic-curation.md

@@ -0,0 +1,33 @@
+---
+title: "Moonshot — Fully Agentic Curation"
+domain: generative
+collection: _drafts
+status: draft
+confidence: low
+created: 2026-05-18
+updated: 2026-05-20
+updated_by: agent:claude-code
+provenance: inferred
+sources: []
+superseded_by: null
+ttl_days: 30
+tags: [moonshot, agentic, curation, speculative]
+questions_answered: []
+questions_raised:
+  - "What is the smallest curation loop an agent can run end-to-end without human review?"
+---
+
+# Moonshot — Fully Agentic Curation
+
+Speculative sketch. A generative-domain note: this is not a claim about the
+world, it is a draft of a question we might build toward.
+
+Suppose the curator is itself an agent, not a human. What is the smallest
+end-to-end loop — write, lint, deprecate, promote — that an agent can run
+unsupervised before the absence of human review starts to compound errors?
+
+## Questions Answered
+- (none yet — this is a draft)
+
+## Questions Raised
+- What is the smallest curation loop an agent can run end-to-end without human review?

package/templates/reviewer-vault/_drafts/scratch-incomplete.md

@@ -0,0 +1,18 @@
+---
+title: "Scratch — Helios pricing reaction"
+domain: accumulation
+collection: _drafts
+status: draft
+updated_by: agent:claude-code
+provenance: inferred
+tags: [scratch, helios]
+---
+
+# Scratch — Helios pricing reaction
+
+Intentionally-incomplete frontmatter — the `confidence`, `created`, and
+`updated` fields are missing on purpose. `vault_read` still returns the
+file, but `vault_promote` refuses to promote it because the validator
+flags the missing required fields and the missing confidence.
+
+This note is the reviewer's worked example of a refused promotion.

package/templates/reviewer-vault/competitive-intel/aurora-pipelines-positioning.md

@@ -0,0 +1,40 @@
+---
+title: "Aurora Pipelines — Positioning Overview"
+domain: accumulation
+collection: competitive-intel
+status: canonical
+confidence: high
+created: 2026-02-12
+updated: 2026-04-20
+updated_by: agent:claude-code
+provenance: synthesized
+sources:
+  - aurora-product-page-2026-q1
+  - internal-aurora-positioning-deck
+superseded_by: null
+ttl_days: 120
+tags: [aurora, ingestion, pipelines, competitive]
+questions_answered:
+  - "How does Aurora frame the ingestion-vs-transformation boundary?"
+  - "What is Aurora's stance on managed connectors?"
+questions_raised:
+  - "How does Helios Connect frame the ingestion boundary?"
+---
+
+# Aurora Pipelines — Positioning Overview
+
+Aurora Pipelines treats ingestion as an authored artifact: every source-to-sink
+flow is a versioned, reviewed pipeline that lives alongside the rest of the
+transformation graph. The pitch is that pipelines are code, not configuration,
+and the same review discipline applied to transformation logic should apply
+to data movement.
+
+This sits in deliberate contrast to [Helios Connect](helios-connect-overview.md),
+which bundles managed connectors into the control plane.
+
+## Questions Answered
+- How does Aurora frame the ingestion-vs-transformation boundary?
+- What is Aurora's stance on managed connectors?
+
+## Questions Raised
+- How does Helios Connect frame the ingestion boundary?

package/templates/reviewer-vault/competitive-intel/cirrus-realtime-ga.md

@@ -0,0 +1,38 @@
+---
+title: "Cirrus Realtime — GA Capabilities"
+domain: accumulation
+collection: competitive-intel
+status: canonical
+confidence: medium
+created: 2026-03-18
+updated: 2026-05-12
+updated_by: agent:claude-code
+provenance: synthesized
+sources:
+  - cirrus-realtime-ga-launch-post
+  - cirrus-developer-changelog-2026-q2
+superseded_by: null
+ttl_days: 90
+tags: [cirrus, realtime, ga, competitive]
+questions_answered:
+  - "Which preview-program limitations carried through to GA?"
+  - "What latency profile does Cirrus Realtime guarantee at GA?"
+questions_raised:
+  - "How does Cirrus Realtime's GA pricing compare to capacity-tier list?"
+---
+
+# Cirrus Realtime — GA Capabilities
+
+Cirrus Realtime reached general availability with three notable changes from
+the [preview-era scope](cirrus-realtime-preview.md): a published p99 ingest
+latency, a tiered backpressure model, and a managed schema-evolution surface.
+
+The preview-program note remains in the vault for provenance but should not
+be cited as current behaviour.
+
+## Questions Answered
+- Which preview-program limitations carried through to GA?
+- What latency profile does Cirrus Realtime guarantee at GA?
+
+## Questions Raised
+- How does Cirrus Realtime's GA pricing compare to capacity-tier list?

package/templates/reviewer-vault/competitive-intel/cirrus-realtime-preview.md

@@ -0,0 +1,34 @@
+---
+title: "Cirrus Realtime — Pre-GA Preview Notes"
+domain: accumulation
+collection: competitive-intel
+status: deprecated
+confidence: low
+created: 2025-10-04
+updated: 2026-01-20
+updated_by: agent:claude-code
+provenance: inferred
+sources:
+  - cirrus-realtime-preview-program-notes
+superseded_by: competitive-intel/cirrus-realtime-ga.md
+ttl_days: 90
+tags: [cirrus, realtime, preview, competitive]
+questions_answered:
+  - "What is the pre-GA scope of Cirrus Realtime?"
+questions_raised:
+  - "Which preview-program limitations carried through to GA?"
+---
+
+# Cirrus Realtime — Pre-GA Preview Notes
+
+Early-access notes collected during the closed preview program. Kept for
+provenance only: Cirrus Realtime has since reached GA and the preview-era
+behaviour described here no longer matches the released product.
+
+See [the GA writeup](cirrus-realtime-ga.md) for current claims.
+
+## Questions Answered
+- What is the pre-GA scope of Cirrus Realtime?
+
+## Questions Raised
+- Which preview-program limitations carried through to GA?

package/templates/reviewer-vault/competitive-intel/helios-connect-overview.md

@@ -0,0 +1,40 @@
+---
+title: "Helios Connect — Managed-Connector Overview"
+domain: accumulation
+collection: competitive-intel
+status: canonical
+confidence: high
+created: 2026-03-05
+updated: 2026-05-08
+updated_by: agent:claude-code
+provenance: synthesized
+sources:
+  - helios-connect-launch-post-2026-03
+  - helios-developer-docs
+superseded_by: null
+ttl_days: 120
+tags: [helios, connect, ingestion, managed-connectors, competitive]
+questions_answered:
+  - "How does Helios Connect frame the ingestion boundary?"
+  - "What is the pre-GA scope of Cirrus Realtime?"
+questions_raised:
+  - "Where does Helios Connect's pricing curve cross Aurora Pipelines once volume passes 10 TB/day?"
+---
+
+# Helios Connect — Managed-Connector Overview
+
+Helios Connect is the managed-ingestion surface of Helios. Connectors are
+declared as first-class control-plane objects: a YAML descriptor selects a
+source, a sink, and a small set of typed parameters, and the platform owns
+scheduling, retries, schema drift, and backpressure.
+
+The framing is the inverse of [Aurora Pipelines](aurora-pipelines-positioning.md):
+ingestion should *not* be an authored pipeline. It is a managed primitive that
+teams compose, not author.
+
+## Questions Answered
+- How does Helios Connect frame the ingestion boundary?
+- What is the pre-GA scope of Cirrus Realtime?
+
+## Questions Raised
+- Where does Helios Connect's pricing curve cross Aurora Pipelines once volume passes 10 TB/day?

package/templates/reviewer-vault/competitive-intel/northwind-governance-snapshot.md

@@ -0,0 +1,35 @@
+---
+title: "Northwind Data Governance — 2026 Snapshot"
+domain: accumulation
+collection: competitive-intel
+status: canonical
+confidence: medium
+created: 2026-04-01
+updated: 2026-05-10
+updated_by: agent:claude-code
+provenance: synthesized
+sources:
+  - northwind-governance-product-page
+  - northwind-compliance-whitepaper-2026
+superseded_by: null
+ttl_days: 90
+tags: [northwind, governance, compliance, competitive]
+questions_answered:
+  - "How does Northwind expose lineage to downstream consumers?"
+questions_raised: []
+---
+
+# Northwind Data Governance — 2026 Snapshot
+
+Northwind positions itself as the governance layer, not the storage or
+processing layer. Lineage is exposed through a public catalog API; policies
+are declared centrally and enforced at query time by query-engine adapters.
+
+This document is a snapshot of the 2026 GA surface; revisit when the next
+quarterly release lands.
+
+## Questions Answered
+- How does Northwind expose lineage to downstream consumers?
+
+## Questions Raised
+- (none)

package/templates/reviewer-vault/pricing/aurora-pricing-model.md

@@ -0,0 +1,35 @@
+---
+title: "Aurora Pipelines — Pricing Model"
+domain: accumulation
+collection: pricing
+status: canonical
+confidence: medium
+created: 2026-03-22
+updated: 2026-05-04
+updated_by: agent:claude-code
+provenance: synthesized
+sources:
+  - aurora-pricing-page-2026-q1
+  - aurora-enterprise-quotes-anonymized
+superseded_by: null
+ttl_days: 90
+tags: [aurora, pricing, per-pipeline, consumption]
+questions_answered:
+  - "How does Aurora price authored pipelines?"
+questions_raised: []
+---
+
+# Aurora Pipelines — Pricing Model
+
+Aurora prices by the authored pipeline: a flat per-pipeline monthly fee
+covers a published throughput envelope, and excess throughput is metered
+at a per-GB rate. There is no seat component — pricing is volume-driven.
+
+See [Aurora Pipelines Positioning](../competitive-intel/aurora-pipelines-positioning.md)
+for the product framing this pricing rests on.
+
+## Questions Answered
+- How does Aurora price authored pipelines?
+
+## Questions Raised
+- (none)

package/templates/reviewer-vault/pricing/cirrus-capacity-tiers.md

@@ -0,0 +1,37 @@
+---
+title: "Cirrus Capacity Tiers — Pricing Structure"
+domain: accumulation
+collection: pricing
+status: canonical
+confidence: medium
+created: 2026-02-25
+updated: 2026-05-01
+updated_by: agent:claude-code
+provenance: synthesized
+sources:
+  - cirrus-pricing-page-2026-q2
+  - cirrus-capacity-reservations-faq
+superseded_by: null
+ttl_days: 120
+tags: [cirrus, pricing, capacity-tiers, reservations]
+questions_answered:
+  - "How are Cirrus capacity reservations sized?"
+questions_raised:
+  - "At what mix of steady-vs-burst workload do capacity reservations break even against on-demand?"
+---
+
+# Cirrus Capacity Tiers — Pricing Structure
+
+Cirrus pricing is tiered around reserved capacity blocks. A reservation is a
+24/7 commitment of a named capacity class for one or three years, billed at
+a flat hourly rate. Burst above the reservation falls back to on-demand at
+a published premium.
+
+See [Cirrus Realtime — GA](../competitive-intel/cirrus-realtime-ga.md) for
+product context.
+
+## Questions Answered
+- How are Cirrus capacity reservations sized?
+
+## Questions Raised
+- At what mix of steady-vs-burst workload do capacity reservations break even against on-demand?

package/templates/reviewer-vault/pricing/helios-credits-model.md

@@ -0,0 +1,37 @@
+---
+title: "Helios Credits — Consumption Pricing Model"
+domain: accumulation
+collection: pricing
+status: canonical
+confidence: medium
+created: 2025-09-10
+updated: 2025-12-15
+updated_by: agent:claude-code
+provenance: synthesized
+sources:
+  - helios-pricing-page-2025-q4
+  - helios-credits-faq
+superseded_by: null
+ttl_days: 90
+tags: [helios, pricing, credits, consumption]
+questions_answered:
+  - "What unit of consumption does Helios bill against?"
+questions_raised:
+  - "Have Helios credits per-workload-class rates shifted in the 2026 update?"
+---
+
+# Helios Credits — Consumption Pricing Model
+
+Helios bills against a single virtual unit — the Helios Credit — that maps
+to underlying compute via a per-workload-class multiplier. Storage is
+metered separately and not in credits.
+
+This note dates from late 2025 and is overdue for a refresh against the
+2026 pricing page. See [Helios Connect](../competitive-intel/helios-connect-overview.md)
+for product context.
+
+## Questions Answered
+- What unit of consumption does Helios bill against?
+
+## Questions Raised
+- Have Helios credits per-workload-class rates shifted in the 2026 update?

package/templates/reviewer-vault/pricing/vega-pricing-strategy.md

@@ -0,0 +1,36 @@
+---
+title: "Vega Insight — Pricing Strategy Snapshot"
+domain: accumulation
+collection: pricing
+status: canonical
+confidence: medium
+created: 2026-04-10
+updated: 2026-05-15
+updated_by: agent:claude-code
+provenance: synthesized
+sources:
+  - vega-pricing-page-2026-q2
+  - vega-customer-conversations-2026-q1
+superseded_by: null
+ttl_days: 90
+tags: [vega, pricing, seats, hybrid-pricing]
+questions_answered:
+  - "What pricing levers does Vega expose to enterprise buyers?"
+questions_raised: []
+---
+
+# Vega Insight — Pricing Strategy Snapshot
+
+Vega Insight uses a hybrid: per-seat for the analyst surface, per-query for
+the embedded surface, with a published volume discount table. Enterprise
+contracts layer a flat platform fee on top of metered usage.
+
+Sits alongside [Helios Credits](helios-credits-model.md) and
+[Cirrus capacity tiers](cirrus-capacity-tiers.md) as the third anchor
+point in the pricing comparison set.
+
+## Questions Answered
+- What pricing levers does Vega expose to enterprise buyers?
+
+## Questions Raised
+- (none)