Rapid Prototyping Services (Phase 2)

(Description)

Overview

Something

Goals

List main objectives, problems you aim to solve.

Features

• Bill Processing (Admin Section)
• Bam
• SSO For Signing into App

Software Stack / Technologies Used

• Language: python, sql, javascript, html, css
• Framework: react
• Database: aws
• etc...

Quickstart

Summary for developers with links to setup, build, test instructions in wiki or docs.

Instructions

1. Click "Use this template" on GitHub to create your private repository.
2. Clone your repo locally.
3. Fill in the metadata table above.
4. Create an initial branch (e.g., setup), never commit directly to main (unless instructed).
5. Open an Issue for each lab / feature before starting work.
6. Use Pull Requests to merge changes (each PR should reference at least one Issue).

Structure

Include: what constitutes passing (e.g., all tests green, coverage threshold).

Coding & Collaboration Conventions

• Use semantic commit messages (see CONTRIBUTING.md for full details).
• Open an Issue for every distinct unit of work (lab task, feature, bug, refactor, research).
• Create branches from main named after the Issue: <type>/short-kebab (e.g., feat/scheduler-phase1).
• Commit changes incrementally with semantic commit messages.
• Open a Pull Request early (draft) and link the Issue.
• Request peer review (if required) before merging.
• Squash merge or rebase to keep main linear (unless told otherwise).