One ProfileGenderField (女 / 男 / 不填, 44px, one hint line) in the
people-archive edit form (saved with the form, 不填 → null) and in
设置 → 个人资料 for the owner (saves on its own PATCH; birth-data saves never
send gender). The detail card shows 性别 (未填 when empty). Not asked in
onboarding. DESIGN/VOICE updated; 390/1280 screenshots with fictional data.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
The marriage evidence card's gender field is the bound subject's own value
(女 / 男, 性别未知 when not filled). The condensed checklist keeps the
gender-unknown rule only when unset; otherwise it names the spouse
significator per strict-workflow-router.md §4 and the repo's gender
interpretation contract (supplement only, core stack gender-neutral). The
methodology cache is keyed by gender so one person's line never serves
another. Tests drive the real getJyotishAgent with a prompt-recording model.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
20260920020000 added active_birth_date / active_birth_timezone_offset /
active_birth_provenance without a service_role column grant, while the
account PATCH and the report worker's self lookup read them through
service_role (42501, recurrence of BUG-039 / BUG-600). Additive SELECT-only
grant plus a static contract: every profiles column a service_role reader
selects must be granted. BUG-1063 (worker cannot read chart_profiles as
service_role) recorded as investigating, not fixed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
Additive migration: nullable profiles.gender / chart_profiles.gender with a
female/male CHECK, owner-only via existing table RLS, column grants mirroring
the neighbouring birth columns (service_role for the account PATCH, no
admin_runtime). Account PATCH/GET, people POST/PUT/GET, subject resolution
and the consult route carry each person's own value; a people write only
touches gender when the key is sent. DB test runs in the gate's DB job.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
`cmd_double_transit_pac` placed the `D9_{N}宫` target on the D9 lagna sign
and the `D9_{lord}(宫主)` target on that planet's D1 longitude. Both now sit
on D9 signs (D9 house-N sign; the lord's navamsa sign), built in one
testable helper. Target names, D1 and Chandra Lagna layers are unchanged
(pre-fix golden, byte-identical). Evidence-card golden regenerated with the
capture script (one public chart: double-transit conclusions 9 -> 10).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
TASK-consult-evidence-card-v2-20260927 T5. PROGRESS with the native-module
table, the final per-card table, before / after sizes (3 public AA charts x
12 questions, all single-domain turns <= 12,000), red-line tests, failure-name
comparison and three-column edits; real-device checklist; CHANGELOG; task
index row set to 待验收; VOICE / DESIGN name the new lookup labels (no UI
change); BUG-1060 investigating (Double Transit D9 house target reads the D9
lagna; not fixed here, red line 1).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
TASK-consult-evidence-card-v2-20260927 T4 (方案 B). Career, marriage and
wealth hand the answer model a 5-7 line condensed checklist
(frontend/src/lib/consultation-condensed-checklist.ts) in place of the full
strict route plus event-judgment file: must-see items (all on the card),
the three layers (接触 / 结构性机会 / 公开落地; 心动接触 / 关系成对 /
社会法律落地; 挣钱机会 / 真实增长 / 到账变现), the forbidden statements
(5L 大运 ≠ 法律婚, 金星过本命月 ≠ 心动月, Punarphoo 不得写成结婚,
土星回到本命月是观察项), the gender-unknown rule, and the lookups (KP
blocked). The shared baseline still travels; timing / health keep their
full router sections; the router, the event-judgment files, the bound
system method and the skill are unchanged (no skill version change).
Only the consultation tool builds the methodology, so reports and other
surfaces are unaffected (source test).
Single-domain model-visible size, 3 public AA charts x (10 questions +
annual + timing): career 9.8K, marriage 10.5K, wealth 9.9K, annual 11.5K,
timing 11.3K; all <= 12,000.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
TASK-consult-evidence-card-v2-20260927 T3. Card version evidence-card-v2.
- Base section (every card): the engine's D9 summary (D9 lagna, each
planet's D9 sign and dignity, Vargottama, D1/D9 reversals); D9 houses and
aspects stay out.
- Career: + AL (engine pada A1), 10H SAV, SAV of the Jupiter / Saturn
transit signs.
- Marriage: + 5H / 5L, day / night, Punarphoo (observation_only), Double
Transit on 7H / 7L (house-7 run) and DK / UL, Vivah Saham, gender unknown.
- Wealth: 8H / 12H named.
- Annual: the annual Tajika chart verbatim (parameter_sensitive), or
年盘未接入 when the pack is blocked / not attached (never natal data);
houses 1 + running / next AD lords' houses + the year's Jupiter / Saturn
transit houses, with their basis; ingress / station dates only.
- Timing: Rahu / Ketu with ingress dates, Jupiter / Saturn SAV and BAV,
Double Transit conclusions (no degrees); vargas follow the turn's other
domain, D9 when alone.
- Chara Dasha leaves every card; KP is never on a card. The lookup enum adds
karakamsha, dispositor_chains, inter_chart_linkage, argala, moon_transit;
a KP lookup travels with its blocked note.
- System prompt and tool descriptions name the D9 summary, the
parameter_sensitive / observation_only tags, 年盘未接入 and the lookups.
- Telemetry card version / agentVersion bumped to v2 (three-column notes in
the touched tests).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
TASK-consult-evidence-card-v2-20260927 T2. toAgentConsultationContext carries
chart.consultation_native_layers as local_layers.native_layers; toModelOutput
projects d9_summary / punarphoo / vivah_saham / day_night into the natal card
and slow_transits / double_transit / annual_tajika into the timing card, each
through its own nested-key allowlist (as BUG-1054 did for Narayana), so the
existing natal and timing key sets are not widened and the depth / list caps
are unchanged. Pada A1 (the engine's Arudha Lagna) is allowlisted for the
career card's AL.
Golden test: every projected layer equals the engine layer value for value on
3 public AA charts (family, timing and annual routes); the Double Transit
per-house summary line is the only field left out.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
TASK-consult-evidence-card-v2-20260927 T1. New module
scripts/consultation_native_layers.py, thinly registered after the merged
engine fields in _attach_local_consultation_layers (no handler method, no new
forgery site). It writes one new top-level chart key,
chart.consultation_native_layers, kept out of chart.modules so the thematic
report's full_reading_module_count does not move:
- d9_summary: D9 lagna, each planet's D9 sign and dignity
(jyotish_engine._get_dignity_level), Vargottama (_calc_vargottama),
D1<->D9 reversals
- punarphoo (punarphoo.detect_punarphoo, observation_only)
- vivah_saham (jyotish_engine._calc_vivah_saham), day_night (gulika)
- slow_transits: Jupiter / Saturn / Rahu / Ketu now with natal house and the
Jupiter / Saturn SAV / BAV, and the next twelve months' ingress / station
dates (ephemeris_events; nodes by the same daily-noon sampling)
- double_transit: cmd_double_transit_pac for houses 1-12, conclusions only,
plus DK / UL targets by the same PAC rule
- karakamsha, argala, dispositor_chains, inter_chart_linkage, moon_transit
(lookup-only layers)
- annual_tajika on the annual route: build_annual_tajika_pack (annual lagna,
Varshesha, Muntha, Mudda Dasha with dates, Sun / Moon / year-lord Tajika
aspects), parameter_sensitive; blocked when the pack is not reliable,
never natal data
A/B on 3 public AA charts x 4 routes: every existing output is identical,
only the new key is added; about 40 ms per workflow. Golden regenerated with
annual and timing routes (family workflow byte-identical apart from the new
key).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
Research brief reopening the 09-19 Jev evaluation: same model
(jev-1.13.0), only the state changes (previous turn + previous
decision + continuation Noul, per Magpie v0.1.142). Re-extract
source B with case_id; thresholds unchanged.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0199rbQDTsUbCVw84wc8BTFe
Adds rules previously kept only in Claude's local memory so Codex/Cursor
follow them too: path-scoped docs commits (ERR-112), PostgREST compat
layer needs real queries (BUG-990), grep source-text contract tests
before moving code (BUG-933/934/939/992/1014), privacy marker test for
docs with measurements, quick gate for any scripts/tests change, Node
`# cancelled` check (BUG-995), and history-open check on Skill bumps
(BUG-621).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0199rbQDTsUbCVw84wc8BTFe
T7 of TASK-rectification-grounding-20260927. Skill not bumped (10.0.31 text
unchanged, sliced per turn). regenerate_agentic_rectification_turn kept, to be
retired in a later brief.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
T6 of TASK-rectification-grounding-20260927.
- skill-slice.ts: per-action slice rule as a code constant, keyed on heading
titles (evidence: 「ConversationFocus 与意图承接」「批量证据与日期真实性」, i.e.
§5/§7 of the 10.0.x layout); other actions and any bound Skill without those
headings (9.0.0) get the whole body, so historical Cases still run with their
exact bound Skill (BUG-621).
- The rectification Agent declares providesSkillDiscovery "on-demand"
(rectificationSkillBoundProcessor): no <available_skills> block with a temp
path and no "call the skill tool" system message; getSkill still loads the
bound package.
- Measured on a real Agent + recording model (public AA case, estimate = CJK
chars + other chars / 4): fixed overhead per call 12,002 → 6,471 tokens
(step 0: 8,440 → 2,909). Skill text unchanged; no version bump.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
T5 of TASK-rectification-grounding-20260927.
- rectification-offer-candidates returned the full projection (~100 KB on the
public AA case: *_pre_inference, 31 KB contrast packet, probe lists). It now
returns the compare stripping (offerModelProjection); 100,012 → 28,799 bytes.
- agentVisibleLatestProjection also drops engine_indistinguishable_width_minutes
(audit-only since BUG-593), keeps the verification Markdown once
(skill_verification_report; range_delivery.verification_markdown was a
byte-identical copy) and shows the slim candidate list.
- Receipt fingerprints stay over the full payloads; the case API projection
(latestResultToolProjection) is unchanged.
Contract tests on a real local engine response (public AA chart).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
T3 of TASK-rectification-grounding-20260927 (red line 3).
The turn-decision read-case is the model's only conversation memory; with
about 7+ candidates (9 in the public AA case) it exceeded 6 KB and cleared
recent_turns and relevant_evidence_summary first. Candidates in the
model-visible inference now carry time / score / status / cluster_range only
(the last round names candidates by time), candidate_summary.candidates (a
duplicate) is gone, and over budget the order is: drop cluster ranges → keep
the best six candidates → shorten turns/evidence → clear them. Stored
inference and receipts are untouched.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
T2 of TASK-rectification-grounding-20260927 (product decision P1).
The rectification 「重试（重新生成）」 was a blind agent.generate rewrite that
persisted unchecked text (invented range / fit rate reproduced). Removed:
the regenerate route, regenerate-turn.ts, the regeneration agent and its
read-only tool set, the client regenerate action/state and the
regenerating/canRegenerate props. ChatMessageActions renders the regenerate
button only when onRegenerate is passed; ordinary consultation is unchanged.
The DB function regenerate_agentic_rectification_turn is kept (AGENTS §7.6,
retire in a later round). DESIGN.md / VOICE.md updated; source-contract
tests follow with 原值/新值/原因 notes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
T4 of TASK-rectification-grounding-20260927 (BUG-588 / BUG-569 family).
The deferFollowup path persisted the choice before the agent turn, so the
agent turn's prepare read the post-answer range and the deferred choice
narration was never persisted: nobody said the range moved. The typed-message
preflight now hands the pre-answer credible range to the agent turn
(rangeBeforeTurn); the turn's one server range sentence covers the answer and
the dated event. Route-level regression with the real handler.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
T1 of TASK-rectification-grounding-20260927 (recurrence of BUG-588).
- The attempt no longer streams range-changed / rescore-skipped /
compare-failed sentences; the finish whitelists and trims the model body,
then joins the server facts, and emits one final replace equal to the
persisted text.
- P3 whitelist (spoken-grounding.ts): a model sentence with a clock, clock
range or percentage that is not this turn's server fact is dropped whole;
the batch recap stands in when nothing is left.
- record-evidence-batch returns range_after_rescore (post-rescore
credible_range, representative minute, fit percent, delivers_range_this_turn);
the receipt fingerprint stays over the old shape.
- System prompt: range is said by the server; the delivery three sentences
only when the batch says this turn delivers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
PROGRESS with the final domain -> technique table, before/after
model-visible sizes over 3 public AA charts x 10 questions, answer-contract
keys kept/removed, red-line test list, lookup and clock design, telemetry,
assertion changes and test/build/gzip numbers. Device checklist for
parents/children/marriage/career, follow-up domain carry-over, D60 lookup
and waiting time. Task index row set to 待验收.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
After each natal turn the route logs a separate [agent-observability] event
{runId, agentVersion, evidenceCard: {domains, cardVersion, cardChars,
cardTokenEstimate, citedFieldIds, feedback}}. Cited field ids follow the
research R5 rule (ISO date, degree, planet-in-sign phrase of 8+ chars
appearing verbatim in a finished answer); matched text is discarded. Thumbs
are client state only today, so feedback is "none"; storing thumbs per turn
needs a table and is left to a follow-up. The strict schema has no user,
session, question or answer field.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
read-consultation-evidence returns one closed-enum section (a formal varga,
research/extended vargas, a Western layer, yogas, Ashtakavarga, Shadbala,
transits, Chara Dasha, arudha, karakas, KP, gulika, kakshya, mahadashas,
thematic evidence) from this request's finished calculation, never
recalculates, answers unavailable on a cache miss and refuses a second call.
The receipt records the step and the write row shows 「正在多看一眼：…」.
A lookup after answer text went out keeps the released text whole: a verbatim
restart is dropped as it arrives (40-char confirmation), a continuation is
kept, and settlement still reads the step that wrote the answer; the lookup
runs on the answer clock without resetting it. A length continuation carries
the lookup result with the card. BUG-1059: the visible-text transformer's open
clause is settled at each tool call, so unpunctuated narration no longer
leaks into the answer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
The natal system prompt now says: the card in claim_cards is the chart
evidence for this answer, quote it as given, look up one further section of
this calculation with read-consultation-evidence before writing, and read
evidence_card.backstage as a confidence cap. The "use every executed layer"
and must_use_layers sentences are replaced; local_layers paths now point at
the card. SKILL.md 关联技法完整调取 / 0.0.1 and router 0.7 state that the
full result stays in receipts, the 本轮技法 panel and reports while web chat
answers from the card; computing the full spectrum is unchanged. Skill and
package version 6.9.16 -> 6.9.17 (tests/run_all.py 三栏).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
New frontend/src/lib/consultation-evidence-card.ts ports the research
CARD_SPECS: base section (ascendant, house signs, placements with degrees,
functional benefics/malefics with lordship, Vimshottari MD/AD/PD with dates,
Narayana md/ad/pd) plus a section per domain; values copied verbatim from
the projection or engine context, gaps listed, never filled. The tool now
returns toModelEvidenceView: status, evidence_contract (policy, blockers,
layers, limitation), claim_cards = the card, evidence_card meta (D4 line,
supplementable sections), rectification, methodology, domains; the audit
table, spectra, must_use_layers and presentation stay server-side and the
single-domain consultations copy is gone. 「本轮技法」 rows are unchanged.
Golden tests over three public AA engine captures.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
parents (D12, 4/9 houses, Sun/Moon) and children (D7, 5th house, Jupiter,
PK) are plan/card domains with Chinese labels and the brief's aliases. They
send the family route contract to the engine and are rejected as a stored
session theme, so neither Python nor the chat_sessions.theme CHECK changes.
Methodology reports no strict checklist for them; must-use layers follow the
plan domain. Tests with 原值/新值/原因 where assertions changed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
timingKeys now admits current_dasha.md/ad/pd (sign, lord, years,
start_age, end_age), remaining_years and pratyantar_dasha_timeline. Depth
and item caps unchanged. Golden regression over three public AA engine
captures asserts values, not key presence.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
Gate run 2958 failed tests/test_api_server_growth_contract.py: the
evidence-card research script added two JyotishAPIHandler forgery sites.
Reuse capture_report_blocked_repairs_golden._handler(); output unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017eEAG8HD3mm8gsKXgk8uU8
Measure the model-visible consultation payload on three public charts, draft per-domain cards, and record the Narayana/pratyantar projection gap as BUG-1054. No runtime behavior change.
