Hunpeo LabsStart a project

Gig / Release intelligence

Open-source engineering project

Know what changed.Know what shipped.

Trace source change to production truth in one reviewable trail.

Replay a releaseView source
  • Open source
  • Evidence-first
  • Traceable
  1. 01TicketABC-123
  2. 02Commita1b2c3
  3. 03Checks7f9d2e1
  4. 04Deployd3e4f5a
  5. 05Productionprd-9a8b7c
00:14 / Release traceReview ready
  1. 01TicketABC-123
  2. 02Commita1b2c3
  3. 03Checks7f9d2e1
  4. 04Deployd3e4f5a
  5. 05Productionprd-9a8b7c
A real Gig demo moving from ticket inspection to release evidence.

01 / The problem

A release is more than a green check.

Source, delivery, and production evidence belong in one story.

TicketABC-123Commita1b2c3Checks7f9d2e1Productionprd-9a8b7c
TicketABC-123Commita1b2c3Checks7f9d2e1Deployd3e4f5aProductionprd-9a8b7c

From change to truth.

  1. 01Source changeFind the ticket.
  2. 02Release pathFollow delivery.
  3. 03EvidenceCollect checks.
  4. 04Production stateConfirm what is live.
  5. 05ReviewInspect the trail.

Release truth graph

See the whole trail. Then inspect any step.

Ticket, commit, checks, delivery, and production state remain connected.

Review ready
  1. 01TicketABC-123
  2. 02Commita1b2c3
  3. 03Checks7f9d2e1
  4. 04Deployd3e4f5a
  5. 05Productionprd-9a8b7c
Selected stepCommit a1b2c3Author · date · release intent
Commit diff
+ validate release()
+ record evidence()
+ require approval()
Check resultAll checks passedLint · unit · integration · build
DeploymentDeploy d3e4f5aEnvironment and revision recorded
Production confirmationState recordedEvidence ready for review

02 / What Gig connects

  1. Trace the changeLink a ticket to its source changes.
  2. Follow deliveryMap the release path end to end.
  3. Collect evidenceKeep checks beside the release step.
  4. Confirm productionRecord the reviewable production state.
  5. Review the storyInspect the complete release truth graph.

Release confidence starts with traceability.

03 / Current boundary

Open source. Evidence first.

An engineering project focused on inspectable release paths—not unverified production claims.

Where is the source?

The verified public source is available on GitHub.

What evidence can Gig trace?

Source changes, the release path, checks, production state, and review evidence.

How does the trace work?

The gig trace command builds a release truth graph for one ticket.

How do I report an issue?

Use the public GitHub issue tracker so the report stays connected to the source.

Inspect the release trail.

View GitHubRead the demo guide