Skip to content

About

Public-ready Workforce Intelligence hackathon platform

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

686 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Workforce Intelligence Platform

Public-ready hackathon monorepo for an AI-assisted workforce operations system. The project combines attendance workflows, biometric verification, browser/device signals, AI copilots, and an operations command center into one demoable platform.

What Is Inside

Area Path Purpose
OAS web app HRS/OAS_project ASP.NET Core attendance, shifts, approvals, admin workflows, and employee self-service.
Command Center CommandCenter React/Vite operations cockpit for agent chat, workflow visibility, reports, and live-assist surfaces.
AI Engine ai-engine TypeScript/Hono service for AI providers, Vertex/Gemini integrations, OCR/image flows, and live-agent support.
Agent Orchestrator agent-orchestrator Python agent harness for tool planning, guardrails, streaming, and policy checks.
Browser Fingerprint CheckBrowser Device/browser fingerprint API and client demo.
Face Services FacialRecognition, FaceEnginePy Node and Python face verification/identification services.
Docs docs, root *.md reports Architecture notes, testing guides, demo checklists, and readiness plans.

Architecture

Employee/Admin UI
  -> OAS web app
  -> Agent Orchestrator
  -> AI Engine
  -> AI providers / OCR / image / live services

OAS also integrates with:
  -> Face verification services
  -> Browser fingerprint service
  -> SQL Server / Redis / optional Cloudflare services
  -> Command Center dashboard

Security And Secrets

This repository is intended to be public-source safe. Do not commit local credentials.

Use .env.example files as templates, then create local .env files per service:

cp HRS/OAS_project/.env.example HRS/OAS_project/.env
cp ai-engine/.env.example ai-engine/.env
cp CheckBrowser/server/.env.example CheckBrowser/server/.env
cp FaceEnginePy/.env.example FaceEnginePy/.env
cp FacialRecognition/.env.example FacialRecognition/.env

Never commit:

  • .env or .env.*
  • Google service-account JSON files
  • Cloudflare tunnel credentials.json
  • private keys, certificates, or local binary tunnel clients

Before publishing a fork or public repository, rotate any credentials that ever existed in Git history. See Public Release Checklist.

Prerequisites

  • Node.js 18+
  • Python 3.10+
  • .NET SDK compatible with HRS/OAS_project
  • SQL Server or LocalDB for OAS
  • Redis or Upstash Redis for production-like cache/backplane flows
  • Optional: Google Cloud/Vertex, Cloudflare, Groq, OpenRouter, xAI keys depending on enabled AI providers

Quick Start

Install dependencies and configure environment files first.

# OAS web app
cd HRS/OAS_project
dotnet restore
dotnet run
# Command Center
cd CommandCenter
npm install
npm run dev
# AI Engine
cd ai-engine
npm install
npm run dev
# Agent Orchestrator
cd agent-orchestrator
python -m venv .venv
.venv/Scripts/pip install -r requirements.txt
.venv/Scripts/python app.py
# Browser fingerprint service
cd CheckBrowser/server
npm install
node index.js
# Python face engine
cd FaceEnginePy
python -m venv .venv
.venv/Scripts/pip install -r requirements.txt
.venv/Scripts/python -m uvicorn app.main:app --reload --port 8000

Useful Checks

# OAS
dotnet build HRS/OAS_project/OAS_project.csproj

# Command Center
npm --prefix CommandCenter run typecheck
npm --prefix CommandCenter run lint

# AI Engine
npm --prefix ai-engine run build
npm --prefix ai-engine test

# Agent Orchestrator
python -m pytest agent-orchestrator

Run the checks relevant to the services you changed. Some checks require local databases, provider keys, or running companion services.

Documentation

Public Release Notes

The repository previously contained local credential files during development. The tracked files have been removed from the current tree, but Git history may still contain old secret material. Treat exposed keys as compromised and rotate/revoke them before making the GitHub repository public.

About

Public-ready Workforce Intelligence hackathon platform

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages