Silver Rook Labs

Silver Rook Labs portfolio

Small, sharp assets that compound into stronger delivery.

The portfolio is built around practical software: decision tools, paid actors, and open-source workflow utilities that generate evidence, credibility, and reusable operating patterns over time.

View the portfolioSee the operating model
Asset graph5 nodes
Silver Rook Labs portfolio graphFive assets connect to research, revenue, authority, demand, and reusable capability roles.SRLportfolioSignalCartJUnitDriftPower
Live
2
Open source
2
Experiments
1
Roles
4
Direct revenuePaid usage surfaces and exact revenue gates.
AuthorityDeveloper tools that earn trust in public workflows.
Demand captureUseful public tools that reveal buyer intent.

Portfolio assets

Each asset has a role, a surface, and a next signal.

01Experiment

Signal Through Structure

Watch a graph decide what a neural network can know.

An interactive graph-learning observatory for the topology-driven tradeoff between long-range information flow and representation collapse.

Role
Technical-authority experiment
Audience
ML engineers, graph-learning researchers, students, and technical hiring reviewers
Format
Browser observatory
Next signal
Public comprehension and qualified technical interest
  • Deterministic small-graph model
  • Exact propagation and spectral diagnostics
  • Editable topology and responsive interaction
Open asset
02Live

Portable Generator Selector

Size a portable generator from outage loads and hard constraints.

A focused selector for homeowners comparing realistic generator capacity, runtime, fuel, and appliance-load tradeoffs.

Role
Demand-capture asset
Audience
homeowners and operators planning resilient backup power
Format
Browser tool
Next signal
Qualified source and completion events
  • Live public tool
  • Analytics-ready funnel
  • Clear customer decision surface
Open asset Repository
03Live

Shopify Variant Cartability Checker

Verify whether an exact Shopify variant can enter cart and reach checkout.

An Apify Actor for Shopify developers and QA teams that checks the observable storefront cart path for a specific product URL, variant ID, and quantity.

Role
Direct-revenue asset
Audience
Shopify developers, QA engineers, and catalog operators
Format
Apify Actor
Next signal
Exact paid-event and revenue truth
  • Public paid Actor
  • Non-owner usage confirmed
  • Dedicated product page
Open asset
04Open source

Failure History for JUnit XML

Keep recent JUnit failures available across CI runs.

A GitHub Action that fingerprints JUnit XML failures, persists bounded history, and reports whether a failing test is new, recurring, or recently resolved.

Role
Authority asset
Audience
maintainers and CI owners using JUnit XML
Format
GitHub Action
Next signal
Developer adoption and support conversations
  • Marketplace listing
  • Open-source repository
  • Release-ready GitHub Action pattern
Open asset Repository
05Open source

Required Check Drift Sentinel

Detect required checks your workflows no longer emit.

A GitHub Action that compares branch rules and rulesets against workflow-emitted check names so maintainers can catch merge-blocking drift before it surprises a repository.

Role
Authority asset
Audience
repository maintainers who depend on required checks
Format
GitHub Action
Next signal
Observation-window adoption signal
  • Marketplace listing
  • Open-source repository
  • Ruleset/check-name drift focus
Open asset Repository

Operating model

Build evidence, then let the next asset inherit it.

  1. 01

    Expose a narrow surface

    Ship a tool with a specific audience, bounded support promise, and measurable user action.

  2. 02

    Watch the signal

    Track usage, inquiries, adoption, and maintenance cost before expanding the product surface.

  3. 03

    Promote the reusable part

    Move repeatable release, telemetry, and quality patterns back into the portfolio system.

  4. 04

    Kill or compound

    Keep the assets that earn evidence. Freeze the ones that only create maintenance drag.

Portfolio fit

Bring the workflow with teeth.

We are most useful where a real operating problem needs custom software, evidence, and a careful path from prototype to dependable system.

Discuss a portfolio fit

Please do not email credentials or sensitive data. Contact begins a conversation, not a commitment of services.