Engineering software and intelligent systems built for technical work where traceability, control and real-world execution matter.
PAMILANGA Labs starts with the workflow, not the technology. We build software around technical work where evidence, geometry, supplier data and project decisions need to stay inspectable.
Our systems sit between engineering, procurement, architecture and manufacturing. Stable tools are released when their contracts are repeatable; uncertain or human-gated decisions remain explicitly visible.
Deterministic technical-bid compliance software for comparing engineering specifications with vendor evidence while preserving source provenance. The stable 1.x evaluator keeps PASS, DEVIATION, MISSING and REVIEW semantics explicit.
Explore BidLint on GitHub ↗Architectural eXecution Framework for transforming existing project geometry, requirements, client standards and rule packs into coordinated, validated architectural documentation.
Discuss AXF ↗A production-oriented CAD system connecting semantic reconstruction and technical design with manufacturing data, schedules, quantities and controlled production-preparation outputs.
Discuss PamiCAD Pro ↗A deterministic specification and recovery framework for supplier, RFQ and procurement workflows, designed to preserve evidence identity and avoid inventing missing historical state.
Discuss SPEC AI ↗Hardware-agnostic industrial visual intelligence for quality-control and edge-processing workflows, initially focused on natural-stone and porcelain production environments.
Discuss R&D ↗The public procurement toolchain keeps currency normalization, quotation comparison, payment exposure, vendor risk and technical compliance independently inspectable.
Signals only converge at the decision layer. This avoids hiding commercial and engineering logic inside one opaque recommendation.
Auditable FX normalization for supplier quotations with original amount, rate and date provenance.
GitHub ↗Transparent quotation comparison across price, lead time and payment terms using an explicit scoring model.
GitHub ↗Structured buyer-exposure and commercial-risk signals from free-text supplier payment terms.
GitHub ↗Transparent risk scoring across delivery, quality, commercial, compliance-event and dependency signals.
GitHub ↗Evidence-backed technical compliance kept independent from commercial supplier scoring.
GitHub ↗Policy-aware orchestration that combines independently inspectable signals into an explainable supplier decision.
GitHub ↗Outputs stay traceable to the source that supports them.
Ambiguity and qualified review are surfaced rather than silently automated.
Products begin with real engineering friction, not technology demonstrations.
A useful system should move work forward through decisions, files, schedules, packs or actions.
We publish bounded engineering tools when transparent rules, visible limitations and reproducible decision contracts are more valuable than a closed black box. Private product development remains private until the product boundary is ready.
We work on technical workflows where fragmented evidence, repetitive manual work or weak traceability creates measurable operational friction.