Six co-founders cover product algorithms, built-environment fit, software, hardware, flight-control finance and mathematical validation. The project initiator connects strategy, capital and the innovation ecosystem.
Authorisation: Guo Danrui’s biography and portrait are confirmed by him for public use. Other founders and advisors remain subject to their own authorisation and document checks. Schools, alumni associations, foundations, employers or contests listed here are not institutional endorsements.
This page writes facts that are authorised, or that the project supplied and still marks pending verification. Potential academic contacts stay on the research page as public-direction matches. They are not team members. Titles that have not been contractually agreed — “advisory unit”, “strategic shareholder” — do not appear here. Value sits in a duty-domain charter, stage sign-off and cross-module interfaces, not in a ranking.
A confined-network inspection robot has to handle structural collision, GNSS-denied localisation, low-light imaging, gas confounders, well-head work and subsidy compliance at once. That is not a one-person programme. Duty domains are written so a reviewer can see that algorithms, mechanics, software, hardware, capital and statistical validation each have a named owner — not an empty shell behind a demo reel.
PROJECT INITIATOR
Project initiator
From a venture-governance and capital view, connect technical milestones, the innovation ecosystem and the HK–SZ financing path into a route that can be executed.
Portrait and biography confirmed by Guo Danrui for public use
GUO DANRUI
Guo Danrui
Project initiator
Vice president, Peking University Guangdong Alumni Association
Technology venture investor and mentor
Partner and fund manager, Xccelerate Technology Foundation (XTF)
Responsible for strategy advocacy, ecosystem access, financing path and venture-governance advice. Biography and portrait are confirmed by him for official PipeGuardian introductions. The initiator does not replace founder engineering sign-off, and this listing is not an investment commitment.
STRATEGYECOSYSTEMCAPITALGOVERNANCE
FOUNDING TEAM · 01—06
Six duty domains, one product
The team is not ordered as lead and support. Each co-founder owns a named engineering input, a stage deliverable and a cross-domain interface.
01
张
PRODUCT × ALGORITHM
Zhang Shengqin
CEO · co-founder
Southeast University · Computer science
Duty domain
Algorithms and core program setup; product spine, program architecture and cross-module decisions. Translates “it can fly” into an acceptable task object, and stops un-gated performance sentences from reaching public materials.
Stage output: system requirements, core program baseline, product roadmap
02
凌
ENGINEERING × BUILT ENVIRONMENT
Ling Jiahao
Engineering design · co-founder
City University of Hong Kong · MSc intelligent construction Family background in real-estate design
Duty domain
Fit between UAV and underground civil works; turns construction, O&M and spatial constraints into engineering interfaces. Corridor clearance, well-head working face and asset-coding habits enter mechanical inputs here, rather than as a drawing added afterwards.
Stage output: scene envelope, interface tree, mechanical design inputs
03
梁
SOFTWARE × AUTONOMY
Liang Wentao
CTO · co-founder
HKUST · Business and technology Family background in real-estate design
Duty domain
Programming, algorithms and software design; flight software, PG-Atlas and engineering version control. Loss-of-link state machines, the data dictionary and the release mechanism sit at the same rank as the mechanical prototype.
Stage output: software architecture, data path, version and release mechanism
04
黄
HARDWARE × INTEGRATION
Huang Guozhao
UAV hardware design · co-founder
HKUST · Science Hong Kong identity (biography pending member confirmation)
Duty domain
UAV design and engineering; structure, propulsion, sensors, power and maintainability integration. Cage, quick-release, heat and harness must work with gloves at a well-head.
Stage output: hardware BOM, integrated prototype, inspection and maintenance spec
05
许
CAPITAL × FLIGHT CONTROL
Xu Bosen
Commercial finance and technology · co-founder
Xiamen University · Finance Asia-Pacific AI Innovation Contest UAV gold (certificate pending verification)
Duty domain
Finance and fundraising, UAV flight control; connect capital planning, subsidy filings and technical milestones. The flight-control baseline and the filing ledger must point at the same set of tests, not two stories.
Algorithms and mathematical modelling · co-founder
City University of Hong Kong · PhD mathematics
Duty domain
Algorithms, mathematical modelling and pipe modelling; degraded-environment models, metrics and statistical validation. Localisation drift, gas response and defect models must carry uncertainty, not a single-point number.
Advisors are professional-judgement and risk-control interfaces. They do not replace management. Scope, conflicts, pay, confidentiality and IP follow a formal agreement.
LEGAL / IP
Lara Huang
Background provided by the project: public-fund compliance and legal practice. Advises on legal, financing compliance and IP. Practising credentials, institutions and public titles are confirmed from her own documents. Subsidy stacking, related-party trades and public claims sit inside compliance review.
CAPITAL / VENTURE
Zhang Renzheng
Background provided by the project: private-fund partner, mentor, angel investor, contest judge. Advises on financing strategy, pitching and competitions. Valuation advice stays bound to evidence gates. It does not use a revenue multiple that does not exist.
HOW WE WORK
How a duty domain becomes a product
Cross-module conflict is not settled by rank. It is settled by test metrics and design review. That is the only way “many founders” becomes a governable system.
OPERATING SYSTEM
Write importance into governance
Each owner has a duty-domain charter and stage sign-off;
System interfaces freeze through RACI, drawing/code permissions and version records;
Vesting, background IP, school/employer IP and non-compete are confirmed separately;
Cross-module conflict is decided by test metrics and design review.
LEARNING NETWORK
A research network is not a team endorsement
HK–SZ faculty and institutes are listed separately as potential academic contacts, matched only on public research direction. They are not on the team roster and do not imply collaboration. Using a school name, a professor’s name, a photograph or “joint R&D” in public needs written authorisation.
Pending verification: Huang Guozhao’s biography awaits member confirmation; Xu Bosen’s contest gold awaits a certificate check. Until those checks close, the wording stays “project-supplied / pending verification” and does not upgrade to a confirmed title. Capability needs sit on careers. We hire to reinforce a duty domain. We do not publish a fictional headcount.
INTERFACES BETWEEN PEOPLE
People interfaces need an ICD too
If six duty domains only live on an about page, conflict returns to instant messages. Interfaces have to land on drawing permissions, test metrics and sign-off.
Mechanics and flight control share mass, centre of gravity, vibration and e-stop. Flight control and Atlas share time sync and a telemetry dictionary. Scene engineering and safety share the exclusion list. Finance and technology share the same milestones. The escalation path for a cross-domain dispute is design review, not rank. The initiator offers governance and ecosystem advice. That advice does not replace those signatures.
The same structure protects authorisation. Unconfirmed biographies stay pending verification. Unauthorised portraits stay offline. Potential faculty stay on the research page. The team can be small. It must be auditable. Capability gaps sit on the careers page: we add testing, embedded, gas HSE and data. We do not fill an about page with a fictional roster.
FULL-TIME AND IP
Full-time and IP are a valuation gate, not decoration
The commercial page lists “core team full-time and IP assignment clear” as a valuation-release condition. This page has to explain what that means in operation.
Full-time does not require six founders to drop every outside role at once. It requires accountable hours and a conflict disclosure in each duty domain. School, employer and family-business backgrounds can bring site understanding. They can also bring employee-invention disputes. Those are confirmed separately before a filing, not waved through on a pitch as “alumni”.
Background IP, open-source licences and the origin of design source files enter a ledger. Initiator and advisor scope follow an agreement. They do not automatically become inventors. Unverified contest gold and biographies stay pending verification. Public use of anyone’s portrait, other than Guo Danrui’s confirmed image, takes a separate authorisation. That is respect, and it is compliance.
If a member leaves or a duty domain shifts, the site updates within the authorised scope. It does not keep displaying an expired split. Honesty on the team page and honesty on the product page are the same brand.
