Glance labels are pooled under one caller and question, so easy criteria in one skill earn enforcement for hard ones in another
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
- Domain
- ai-infra-agents
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from danielmiessler/LifeOS
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
danielmiessler/LifeOS#2894 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
danielmiessler/LifeOS#2891 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
danielmiessler/LifeOS#2888 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
danielmiessler/LifeOS#2886 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
danielmiessler/LifeOS#2848 ·
Maintainers usually reply within 5 days
All issues in danielmiessler/LifeOS
Similar issues
-
ready-for-agent
Difficulty 1/5 Under an hour Newbie friendliness 86/100
LucasSantana-Dev/Lucky#3257 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement frontend good first issue help wanted testing-infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
Maintainers usually reply within 1 day