Rhino / Grasshopper Designer–Engineer Brief
Manifold 618 — Phase 1 Digital System Definition
Why this role exists
Manifold 618 has reached a point where its architectural logic, component relationships, and interface strategies are well established and now require consolidation into a rigorous, maintainable parametric system.
This role exists to build that digital foundation.
The work is focused on systematisation: translating a well-developed design intent into a clear Rhino / Grasshopper definition that can support prototyping, fabrication discussion, and future technical development. The objective is not to invent the system, but to encode it precisely, coherently, and robustly.
Project overview
Manifold 618 is a closed, component-driven modular building system developed around engineered interfaces, disciplined geometry, and long-term material integrity.
The system is founded on a finite set of components, consistent junction logic, and clear rules of assembly. Elements are designed to assemble and disassemble cleanly, with attention to tolerance, interface clarity, and the durability of connections over time.
Circularity is embedded by design: components are conceived for longevity, adaptability, and responsible reuse, supported by digital traceability. The work sits at the intersection of architecture, engineering, and fabrication-aware computation, with a focus on precision and buildability rather than stylistic expression.
Project stage and intent
Manifold 618 is in early technical development.
This phase is concerned with establishing a dependable digital system that accurately expresses geometry, interfaces, and assembly logic, and that can act as a reference point for prototype validation and engagement with fabricators.
This is not construction delivery and not certification-led at this stage. It is about building the underlying parametric structure from which those later processes can follow efficiently and without rework.
Design foundation
The work will be based on a well-grounded existing design intent package, including:
Established architectural intent
Detailed 2D and 3D CAD material
Reference models and sketches
Early interface and junction logic
Your role is to consolidate this material into a clean, structured, and maintainable parametric definition, rather than to redefine the architectural concept.
Design authority for the overall system remains with the originator. This role focuses on technical systematisation, parametric structuring, and refinement of existing logic.
Data structure and system governance (parametric export)
Manifold 618 is being developed as a governed parametric system, rather than a one-off model.
Applicants should be comfortable structuring Grasshopper definitions so that component geometry, parameters, interfaces, and metadata can be exported in a machine-readable form (for example, structured JSON), not only as drawings or meshes.
This includes:
Assigning persistent component and interface IDs
Separating fixed system rules from variable parameters
Exposing dimensions, materials, tolerances, quantities, and basic metadata as explicit data
Supporting clean export of system information for validation, versioning, and future governance
You are not expected to build databases, BIM platforms, or ontology frameworks.
You are expected to structure the parametric model so that system intelligence can travel beyond Rhino without being re-authored.
Scope of work
The role centres on developing and refining the Rhino / Grasshopper model that underpins the Manifold 618 system.
This includes:
Developing a clear, readable, and scalable Grasshopper definition based on existing design intent
Creating parametric families for core components (structural elements, junctions, interface parts, rails, brackets)
Modelling interfaces with fabrication awareness, including tolerance and assembly sequencing
Implementing defined gasket and seal strategies within the model (profiles, seating depth, compression intent, and edge-condition variants)
Maintaining coherence and control as parameters evolve
Embedding basic component data (IDs, quantities, dimensions, weights)
Supporting structured outputs suitable for schedules, bills of materials, and downstream manufacture
The aim is a fabrication-aware digital system that can be trusted as a technical reference, not a speculative or illustrative model.
What success looks like for Phase 1
By the end of this phase, success would look like:
A single, clean, intelligible Grasshopper definition expressing the core system logic
Parametric component families that clearly separate fixed rules from variable parameters
Selected assemblies resolved to fabrication-intent geometry
Clear boundaries established between system-level decisions and future extensions
This phase is intended to conclude with a defined, reviewable package rather than an open-ended development process.
Tools and technical literacy
Strong experience with Rhino and Grasshopper is essential.
Applicants should be fluent using Rhino as a serious systems and fabrication tool, not solely as a form-making environment.
Relevant experience may include:
Grasshopper for component-based parametric systems
Folded or sheet-based metal workflows
Kangaroo for constraint and assembly reasoning
Karamba3D for preliminary load-path or feasibility checks
Ladybug Tools for early-stage environmental understanding
Awareness of Rhino.Inside.Revit as a future export pathway.
Python or C# scripting in Grasshopper (Beneficial but not required)
Not all tools are required, but a grounded understanding of engineering-oriented Rhino workflows is expected.
Engagement structure
This is a freelance / contract engagement.
Expected effort is approximately 30 working days, delivered either as an intensive package or staged over 10–12 weeks, depending on availability and agreed structure.
The work will include 4–6 structured design review sessions, in person where feasible, otherwise remote. Scope and fees will be agreed clearly in advance, with defined stages.
The intention is that this Phase 1 scope is delivered on a fixed-fee basis, informed by your indicative day rate and the agreed scope alignment.
While collaborative in nature, this is a bounded, professional engagement focused on delivering a specific Phase 1 system package rather than an open-ended retainer.
Successful delivery may lead to subsequent phases (interface refinement, envelope logic, or platform extensions), subject to separate agreement.
Discretion and NDA are required due to the proprietary nature of the system.
How to apply
Please send:
A brief CV or profile
2–3 relevant examples of Rhino / Grasshopper work
At least one example should have progressed to fabrication documentation, CNC outputs, prototyping, or production-intent detailing
A short note describing which aspects of this scope align most strongly with your experience
Availability and indicative fee expectations
Contact:
Lincoln Miles – Architect and Founder
Closing note
Manifold 618 is being developed as a long-term architectural system. This role is intended to establish the digital foundations on which that system can evolve with clarity, integrity, and technical confidence.