• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

StoneCypher / jssm / 7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e
100%
master: 100%

Build:
Build:
LAST BUILD BRANCH: docs_26-07-04_fable-v6-to-v16
DEFAULT BRANCH: master
Ran 27 Jul 2026 04:05PM UTC
Jobs 6
Files 146
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

27 Jul 2026 03:54PM UTC coverage: 100.0%. Remained the same
7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e

Pull #973

github

StoneCypher
docs(specs): checkpoint the org work-visibility corpus design

Design checkpoint for generalizing the timeline_analysis prototype into a
multi-repo corpus and timeline, driven by a real goal: a senior leader who
feels he does not know what engineering is doing.

Ten decisions recorded with rationale. The load-bearing ones:

- Two allowlists, repos and people, because "may proprietary diffs go to an
  LLM" is a policy question the tool cannot answer for itself. Nothing enters
  the pipeline implicitly.
- A GitHub App rather than an Action, since a per-repo Action structurally
  cannot answer "what did this person do across the org". The App's
  repo-selection screen then IS the repo allowlist, natively and with an audit
  trail, which removes a mechanism we would otherwise have built. Kept
  auth-only so it does not become a hosted service.
- Allowlist by stable numeric ID, never by login or owner/name; both are
  renameable and can come to point at someone or something else.
- Work-centric primary view with person as a drill-down, and no aggregate
  per-person number anywhere. An executive without context reads any
  per-person view as productivity regardless of its label.
- The corpus must display what it cannot see. Diff-derived attribution is
  biased directionally, not randomly: it under-credits reviewers, designers
  and mentors and over-credits volume. Demonstrated live while writing this --
  a jssm-only search found one fork PR by a contributor whose actual
  participation was nine design issues in the fsl tracker plus offline
  conversation no query can reach.

Explicitly a checkpoint, not a finished spec. The brainstorm stopped before
proposing approaches; the OPEN section says where to resume and names the two
hazards worth deciding first -- the multi-repo schema shape, and identity
mapping, which could hole three decisions at once if the workplace is not on
GitHub.
Pull Request #973: feat(v6): land the v6 line as 6.0.0-alpha.12 under the alpha dist-tag

3869 of 3869 branches covered (100.0%)

Branch coverage included in aggregate %.

6361 of 6361 relevant lines covered (100.0%)

33378.91 hits per line

Jobs
ID Job ID Ran Files Coverage
1 7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e.1 27 Jul 2026 04:05PM UTC 146
100.0
GitHub Action Run
2 7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e.2 27 Jul 2026 04:05PM UTC 146
100.0
GitHub Action Run
3 7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e.3 27 Jul 2026 04:05PM UTC 146
100.0
GitHub Action Run
4 7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e.4 27 Jul 2026 04:06PM UTC 146
100.0
GitHub Action Run
5 7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e.5 27 Jul 2026 04:06PM UTC 146
100.0
GitHub Action Run
6 7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e.6 27 Jul 2026 04:07PM UTC 146
100.0
GitHub Action Run
Source Files on build 7a78a33d9aca1f17fdf7dbab672b8e31623bbd8e
  • Tree
  • List 146
  • Changed 12
  • Source Changed 0
  • Coverage Changed 12
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Pull Request #973
  • PR Base - main (#DD801CFC...)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc