FaithSchool: AI-supported learning operations

FaithSchool: AI-supported learning operationsFaithSchool: AI-supported learning operations

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Paulo Pierrondi

• Jun 19

FaithSchool: AI-supported learning operations

AI Automation TypeScript

Steele Stonick

• Jul 20

Which AI workflow would you trust in production?

AI Automation agentic workflowautomation

4 voted

44%

5 voted

56%

9 votes

Closed

Emmanuel Munteh

• Jul 21

Full Autonomy!

Harsh Prajapati

• Jul 20

Rentflow-Multi tenant Multi-Property Management system

Backend Development Database Engineering Frontend Development JavaScript PostgreSQL TypeScript

Krunal Pandya

• Jul 21

"Find Your Owner" that's some next level stuff. way to go my friend 🙌

Faadil Boussari

pro

• Jul 19

Day 5/30: MISREGISTER

An operating-room case can still look ready on paper after it has stopped being operationally executable.

I built MISREGISTER to make that gap physical.

CASE 04 is connected to four changing dependencies:

— staffed OR team — sterile instrument set — postoperative ICU bed — remaining operating-room time

As those windows drift apart, the operating list stays unchanged.

The signature moment: the crank freewheels to the end-stop while CASE 04 still reads SCHEDULED.

Only after that failed test does a human re-strike the case as DELAYED or RESEQUENCED.

This is not clinical decision support. It is a synthetic operational prototype exploring the difference between a scheduled slot and executable capacity.

Built with React, TypeScript, SVG, Playwright, Remotion, Claude Code, Kimi, Agent Reach, ChatGPT, and AI33Pro.

Live prototype: https://faadil1.github.io/misregister-day-5/

Source: https://github.com/Faadil1/misregister-day-5

Interaction Design Product Design UI Design Claude React TypeScript

Maty Sandoval

max

• Jul 20

Making readiness physically understandable instead of dashboard-inferred is such a good design goal, that's usually the exact gap that causes people to ignore dashboards in the first place. Curious to see where you take the physical interaction idea next.