A front door to what lives in veda-github-actions. Each entry links out to the
real app and its source — search by name, filter by type or tag, and read what it does (and
where it falls short).
Search, filter and slice a GitHub Projects v2 board — GitHub's own filter vocabulary made clickable, over Table / By Assignee / Timeline views.
◎ Solves A Projects v2 board can only be sliced the way its own UI allows, and any view of it is locked behind a token. This makes the board queryable, sliceable three ways, and shareable as a link.
Level-of-effort / FTE capacity matrix per person, role and Program Increment, with a what-if PI editor and trend charts.
◎ Solves Ends the Word-doc ↔ GitHub double-entry. The issue becomes the only place FTE is written down, and the capacity view is generated from it — so there is nothing left to keep aligned.
Browse the NASA Disasters product algorithms by hazard, sensor, product, modality, date, event or AOI — and file an activation request as a prefilled PR, with the STAC naming standard enforced as you type.
◎ Solves Makes the product algorithms findable, and catches malformed event names at the keyboard — before a name that merely looks valid writes a wrong hazard tag into a GeoTIFF downstream.
Build an EC2 / S3 / RDS / Lambda estimate on live AWS On-Demand prices — per-resource cards, a grand total in monthly and annual terms, and CSV export.
◎ Solves Gives a cost estimate provenance and a shelf life — every line traces back to the AWS price list version it came from, instead of being a number in a spreadsheet nobody can date.
The three-tab data model, the two entry modes, and the enforcement chain that keeps `YYYYMM_Hazard_Location` honest across rules.ts, validate_data.py and CI.
◎ Solves Answers “why was my valid-looking event name rejected?” — and documents the deliberate, one-directional divergence from upstream DPS validation.
How On-Demand prices are pulled from the public Price List Bulk API with no AWS credentials, published to the aws-pricing/data branch, and reviewed weekly for spikes.
◎ Solves Answers “can I trust this price?” — traces a number on the dashboard back to the SKU and price-list version it came from, with no AWS credentials involved.
The tab/subtab config shell, meeting recurrence resolution against the sprint calendar, timezone handling, and the Changes cart → prefilled PR flow.
◎ Solves Answers “why did this recurring meeting land on that date, in that timezone?” — recurrence resolution against the sprint calendar, and the placeholder dates it currently rests on.
Short ADRs, newest first: why this catalog is Astro rather than the house React stack, why theming goes through data-theme + CSS variables, why adding a person is a prefilled PR rather than a backend, and why every dashboard is its own Netlify site.
◎ Solves Answers “why is it built this way?” before you change it — the reasoning each convention was protecting, so a fix doesn't quietly undo one.
How the FTE capacity report gets its numbers: the `## LOE/FTE` issue-body table versus the PI/date board fields, weighted FTE, the PI-change test loop, and how to reset and reseed.
◎ Solves Answers “where did this FTE number come from?” — which half of the join (issue body table vs board field) owns each value, and how to reshape a board so the report can read it.
The cell-fill-colour status map, per-person overrides, and the two automatic paths from spreadsheet or override PR to the live dashboard.
◎ Solves Answers “why is this person's leave wrong?” by writing down the one non-obvious rule: status is the cell's fill colour, so the fix is a colour, not text.
How the sub-issue crawl works: Objective → sub-issue hierarchy → closing PRs, the global alias-batched BFS, cross-repo traversal, output file naming, and the seed harness.
◎ Solves Answers “why did the crawl miss this PR?” — whether it was depth, the API call cap, an unreadable repo, or a link that isn't actually a closing reference.
Tabbed hub for the Data Services & Enablement group: a timezone-aware meeting tracker (list / calendar / categories) and a PI roadmap, edited through an in-app changes cart.
◎ Solves Puts the group's meetings and PI schedule in one place, in your timezone, laid against the sprint calendar — and lets anyone correct it without a login or a backend.
Month calendar of who is out, a build-your-own person calendar, and a team-risk heatmap with a live coverage threshold — plus add-a-person via prefilled PR.
◎ Solves Frees leave data that only existed as spreadsheet cell colours — so "who's out that week" and "is this team covered" become answerable instead of eyeballed.
Browse accumulated PR-per-Objective reports with a PI/sprint report picker — which pull requests actually closed the work under each Objective.
◎ Solves Follows an Objective's sub-issue tree across repos, orgs and projects — the one thing GitHub's own UI won't do — and reports the PRs that actually closed the work.
No entries match. Try a different search or clear the filters.