Semiconductor IP-Provenance GCC Blueprint Director

The mandate

The company wants India teams to own accelerator blocks and firmware, but existing repositories mix licensed cores, founder-era code, open contributions and customer-specific optimisations with inconsistent origin records. Legal restrictions are translated into broad access denial, forcing duplicate work and weak verification context. Leadership needs a buildable IP operating model before new work packages and external contributors multiply ambiguity.

The five-month deliverable includes an IP-provenance architecture, three complete work-package designs and an exercised contribution-control kit. Milestone one maps origin and decision use by week four; milestone two fixes access and contribution boundaries in month two; milestone three tests contamination and supplier-change scenarios in month four; milestone four delivers rollout, roles, economics and accepted artefacts.

The client will provide repository histories, component bills, licence determinations from counsel, invention records, contributor agreements, supplier rights and access to silicon and firmware owners. Acceptance requires India leads to classify two unseen contribution paths, contain one simulated provenance break and preserve a complete design context. Legal, silicon and security executives jointly sign the work-package envelopes.

The consultants will not issue IP or licence opinions, inspect unauthorised code, select suppliers, determine inventorship or implement repository controls. They may translate counsel’s determinations into operating workflows but cannot grant access or approve a contribution. All exercises occur in client-created sandboxes using representative metadata and authorised artefacts.

Outputs include editable provenance schemas, access patterns, clean contribution flows, work-package canvases, escalation rules, role profiles and transfer gates. Client engineers must adapt the kit to a fourth block in the closing workshop. Implementation and legal remediation are separately commissioned, and acceptance cannot depend on continued access to the consulting team.

Why this is external work

Founders, suppliers and functional owners each hold part of the IP history, while prospective India leaders are excluded from the evidence needed to design their remit. Counsel can determine rights but does not own engineering workflow. Independent silicon operating expertise can create coherent work packages without making legal conclusions.

What you will own

• Map RTL, verification, firmware and tool artefacts by origin, licence determination, contributor, product use and access need.
• Define complete India work packages that preserve architecture and verification context within authorised IP boundaries.
• Design provenance, clean contribution, review, containment and escalation workflows around counsel-supplied determinations.
• Separate engineering ownership, legal interpretation, security administration, supplier obligation and inventorship decisions.
• Establish India IP-aware technical leadership and specialist training without reducing roles to isolated clean-room tasks.
• Exercise unknown-origin code, supplier licence change, accidental access and contaminated contribution scenarios.
• Deliver three work-package envelopes, provenance architecture, control kit, talent plan, economics and unresolved legal inputs.

Candidate qualifications

• Designed semiconductor engineering workflows across proprietary RTL, third-party cores, firmware and open-source components in shipped products.
• Built India silicon capabilities inside complex IP-access and contribution boundaries without fragmenting technical ownership.
• Converted counsel’s licence and ownership determinations into usable repository, review and escalation controls.
• Contained an IP-provenance failure while preserving evidence, product continuity and independent investigation.
• Resolved supplier and founder-code ambiguity before transferring complete design or verification work packages.
• Delivered control artefacts that silicon, legal and security teams operated without continuing consultant interpretation.

Non-negotiables

• Can complete two India residencies and all four Tel Aviv IP milestones within five months.
• Will disclose semiconductor, IP-vendor, open-source, supplier, legal-technology and investor relationships.
• Brings silicon IP-provenance and India work-package design; generic software asset management is insufficient.
• Accepts counsel-controlled determinations, authorised sandboxes and joint legal-silicon-security acceptance.

1. 49 words maximum. Describe a silicon contribution you quarantined because provenance could not support authorised product use.
2. 49 words maximum. Which IP decision belongs to counsel, and which resulting workflow choice belongs to engineering?
3. 49 words maximum. What repository and licence evidence must the client provide before your first milestone?