Glance labels are pooled under one caller and question, so easy criteria in one skill earn enforcement for hard ones in another

Open
#2,762 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 5 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Read skills/Assay/Tools/Proof.ts and LIFEOS/TOOLS/lib/LabelStore.ts, focusing on GLANCE_QUESTION, how Glance labels are filed, and how earnedStatus({ caller, question }) gates enforcement. Trace how a skill and criterion identify each check, then assess a narrower label key while retaining pooled counts for reporting. Done means checks only enforce based on relevant labels; no tests or test files are named in the issue.

Written by the indexing model from the issue text.

Description

What happens

Every Glance check that Proof.ts runs is asked under one caller and one question: caller proof, question intent (skills/Assay/Tools/Proof.ts, GLANCE_QUESTION = "intent"). The principal labels that LabelBatch files for those checks land on that same key, and earnedStatus({ caller, question }) (LIFEOS/TOOLS/lib/LabelStore.ts) counts agreement over all of them together.

So agreement is pooled across every skill and every criterion. Easy criteria in one skill (a name is present, a date is in the header) can carry proof/intent over the bar, and the caller then enforces on hard judgment criteria in another skill that never earned anything on their own.

Expected

A Glance check earns the right to block on labels about checks like it, not on labels about any check in any skill.

Possible fix

File and read Glance labels by a narrower key: per skill and criterion (the check id plus the intent or skill it came from), or at least per class of criterion, with the pooled count kept as a report and not as the gate.

🤖 Generated with Claude Code

Dominant language
TypeScript
Stars
19.9k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.