mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-03 00:52:32 +00:00
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
50 lines
1.7 KiB
Python
50 lines
1.7 KiB
Python
"""Attribution for artefact writes — who (or what) produced a row.
|
|
|
|
Kept in its own stdlib-only leaf (no Django, no pydantic) so any artefact-store consumer can
|
|
import it without dragging the heavy models module. Re-exported from `models.py` for existing
|
|
importers.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
from dataclasses import dataclass
|
|
from typing import Literal
|
|
|
|
|
|
@dataclass(frozen=True)
|
|
class ArtefactAttribution:
|
|
"""Who (or what) produced an artefact — exactly one of a user, a task, or the system.
|
|
|
|
Required on every artefact write helper so no write site can silently skip attribution:
|
|
callers must consciously pick `from_user` / `from_task` / `system()`. System attribution
|
|
covers pipeline writers with neither in scope (e.g. the safety judge); it stores NULLs,
|
|
indistinguishable from legacy rows by design.
|
|
"""
|
|
|
|
kind: Literal["user", "task", "system"]
|
|
user_id: int | None = None
|
|
task_id: str | None = None
|
|
|
|
def __post_init__(self) -> None:
|
|
match self.kind:
|
|
case "user":
|
|
valid = self.user_id is not None and self.task_id is None
|
|
case "task":
|
|
valid = self.task_id is not None and self.user_id is None
|
|
case _:
|
|
valid = self.user_id is None and self.task_id is None
|
|
if not valid:
|
|
raise ValueError(f"ArtefactAttribution kind {self.kind!r} does not match its id fields")
|
|
|
|
@classmethod
|
|
def from_user(cls, user_id: int) -> ArtefactAttribution:
|
|
return cls(kind="user", user_id=user_id)
|
|
|
|
@classmethod
|
|
def from_task(cls, task_id: str) -> ArtefactAttribution:
|
|
return cls(kind="task", task_id=str(task_id))
|
|
|
|
@classmethod
|
|
def system(cls) -> ArtefactAttribution:
|
|
return cls(kind="system")
|