Skip to content

kmishra1204/workgrid-portfolio

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

24 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

WorkGrid Portfolio

A work management platform for permissioned boards, portfolio rollups, workflow approvals, dependencies, notifications, and delivery status views.

This repository is maintained by Karunanidhi Mishra as a professional OSS-oriented enterprise product foundation. It is intentionally nativized away from inherited demo branding and paid-service promotional framing. The goal is to make the product easy for developers to understand, run, extend, and replace paid provider dependencies with open or self-hosted alternatives where practical.

OSS Discovery And Contribution

This codebase is part of Karunanidhi Mishra's Enterprise OSS Product Foundry - a public portfolio of production-minded, enterprise-ready product foundations. It is designed for developers who want to learn from real application surfaces, fork practical patterns, and replace paid SaaS dependencies with open or self-hosted alternatives where possible.

Codespaces And Docker

This repository now includes a GitHub Codespaces/devcontainer path for contributors who want an isolated setup.

  • Open in Codespaces from the GitHub Code button.
  • The devcontainer uses Node.js 20 and includes GitHub CLI plus Docker-outside-of-Docker support.
  • On attach, it runs the static enterprise readiness check.
  • Runtime installs remain explicit so contributors understand when dependencies and provider SDKs are being installed.

Details: Codespaces And Docker

Architecture Signal

WorkGrid Portfolio enterprise foundation map

This visual summarizes the maintainer intent: make the repository readable, forkable, reviewable, and practical for enterprise-minded developers.

AAIF-Adjacent Agentic Readiness

This repository now publishes an AAIF-adjacent readiness surface for developers who care about agentic AI governance, tool boundaries, and enterprise OSS maturity.

The goal is to make the repo useful in technical AAIF/LF-style conversations by showing evidence: setup, security, provider alternatives, auditability, human review, and contribution paths.

Product Scope

Enterprise Setup Target

Next.js work app, relational workflow model, notifications, audit trail, portfolio dashboards, API integration layer.

Developer Quickstart

Prerequisites:

  • Node.js 20+ or the runtime version required by this package.
  • Package manager: npm
  • A local .env.local created from the documented example file when one exists.
  • No real credentials committed to Git.

Run:

cd workgrid-portfolio
npm install

Common checks:

npm install
npm run lint
npm run build

Environment Setup

Example environment files found:

  • None found yet.

Known environment variable names from examples:

No example environment file was found yet. Create .env.local only after reading the provider map and never commit real secrets.

Use local-only .env.local files or a secret manager. Keep real provider keys out of GitHub, README files, issues, and screenshots.

Paid-Service Risk And OSS Alternatives

Paid or closed-service risk areas:

  • hosted auth
  • payments if present
  • hosted database

Open-source or self-hosted replacement direction:

  • PostgreSQL
  • Keycloak compatibility
  • self-hosted notification queue
  • OpenProject/Plane comparison

Provider rule: any paid service must be behind an adapter, have a local development path, and include explicit cost/rate controls before production use.

Runtime Proof

Runtime proof exists. Review docs/RUNTIME_PROOF.md for current command evidence.

The portfolio proof runner is:

powershell -NoProfile -ExecutionPolicy Bypass -File C:\Users\rdpadmin\Documents\Karuna-SEO-PersonalPR\scripts\run-runtime-proof.ps1 -RepoName workgrid-portfolio -WriteProductProof

Contribution Model

Contributions should improve this codebase as an enterprise product foundation:

  • Replace inherited demo wording with product-specific language.
  • Improve local setup and documentation.
  • Add OSS/self-hosted provider adapters.
  • Reduce hard dependency on paid SaaS.
  • Add tests, typechecks, health checks, audit events, and secure defaults.
  • Keep secrets out of the repository.

Modernization Backlog

See docs/ENTERPRISE_TRANSFORMATION.md, docs/PROVIDER_REPLACEMENT_PLAN.md, and docs/RUNTIME_PROOF.md for the current enterprise transformation state.